Platform changelog

What we did: Added a new “possible bounty” variable to message templates, so templates can automatically include the estimated bounty amount for each submission.

Why we did it: This reduces manual edits and copy-paste errors when communicating payout expectations, and makes it easier to reuse consistent messaging across submissions (including when procurement or approvals are involved).

Who it helps: Security teams informing researchers about upcoming payouts, and larger organizations that need procurement involvement or internal approval before issuing a payout.

Note: The “possible bounty” is an estimate shown before acceptance. The final payout can differ in some cases, for example in PTaaS programs where the bounty can be lower than the possible bounty if the bounty pool is empty.

What we did: Added a new “possible bounty” variable to message templates, so templates can automatically include the estimated bounty amount for each submission.

Why we did it: This reduces manual edits and copy-paste errors when communicating payout expectations, and makes it easier to reuse consistent messaging across submissions (including when procurement or approvals are involved).

Who it helps: Security teams informing researchers about upcoming payouts, and larger organizations that need procurement involvement or internal approval before issuing a payout.

Note: The “possible bounty” is an estimate shown before acceptance. The final payout can differ in some cases, for example in PTaaS programs where the bounty can be lower than the possible bounty if the bounty pool is empty.

What we did: Added a new “possible bounty” variable to message templates, so templates can automatically include the estimated bounty amount for each submission.

Why we did it: This reduces manual edits and copy-paste errors when communicating payout expectations, and makes it easier to reuse consistent messaging across submissions (including when procurement or approvals are involved).

Who it helps: Security teams informing researchers about upcoming payouts, and larger organizations that need procurement involvement or internal approval before issuing a payout.

Note: The “possible bounty” is an estimate shown before acceptance. The final payout can differ in some cases, for example in PTaaS programs where the bounty can be lower than the possible bounty if the bounty pool is empty.

What we did: Added a new “possible bounty” variable to message templates, so templates can automatically include the estimated bounty amount for each submission.

Why we did it: This reduces manual edits and copy-paste errors when communicating payout expectations, and makes it easier to reuse consistent messaging across submissions (including when procurement or approvals are involved).

Who it helps: Security teams informing researchers about upcoming payouts, and larger organizations that need procurement involvement or internal approval before issuing a payout.

Note: The “possible bounty” is an estimate shown before acceptance. The final payout can differ in some cases, for example in PTaaS programs where the bounty can be lower than the possible bounty if the bounty pool is empty.

What we did: Added a new “possible bounty” variable to message templates, so templates can automatically include the estimated bounty amount for each submission.

Why we did it: This reduces manual edits and copy-paste errors when communicating payout expectations, and makes it easier to reuse consistent messaging across submissions (including when procurement or approvals are involved).

Who it helps: Security teams informing researchers about upcoming payouts, and larger organizations that need procurement involvement or internal approval before issuing a payout.

Note: The “possible bounty” is an estimate shown before acceptance. The final payout can differ in some cases, for example in PTaaS programs where the bounty can be lower than the possible bounty if the bounty pool is empty.