User Age Verification for Wallet Software #2128
+39
−0
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,39 @@ | ||
| BIP: 1043 | ||
| Title: User Age Verification for Wallet Software | ||
| Author: Brigson | ||
| Status: Draft | ||
| Type: Informational | ||
| Created: 2026-03-21 | ||
|
|
||
| ## Abstract | ||
|
|
||
| This BIP proposes a standard for wallet software to optionally store | ||
| a user-declared date of birth as a wallet metadata field, allowing | ||
| downstream applications to perform age-based access controls in | ||
| compliance with regional regulations such as California AB-1043. | ||
|
|
||
| ## Motivation | ||
|
|
||
| A growing number of jurisdictions require software to implement age | ||
| verification mechanisms. A standardized field would allow ecosystem-wide | ||
| compliance without requiring repeated per-wallet implementation effort. | ||
| The field is self-declared — it is the responsibility of the consuming | ||
| application to determine whether further verification is required. | ||
|
|
||
| ## Specification | ||
|
|
||
| Wallet implementations MAY include a `birthDate` field formatted as | ||
|
Contributor
There was a problem hiding this comment. "birthDate" is already used by some wallets to indicate the date the wallet was created, in order to provide a hint to blockchain scanning services that there's no point scanning for transaction activity before that point. |
||
| YYYY-MM-DD. The field is OPTIONAL globally and SHOULD only be presented | ||
| to the user when the wallet detects a jurisdiction where age verification | ||
| is legally required. | ||
|
|
||
| ## Rationale | ||
|
|
||
| Self-declared age satisfies the minimum technical requirement of several | ||
| regulatory frameworks requiring only a "reasonable effort" at age gating. | ||
| Stricter verification (KYC) remains out of scope for this BIP. | ||
|
|
||
| ## Backwards Compatibility | ||
|
|
||
| This BIP introduces no consensus changes. Wallets not implementing this | ||
| field remain fully compatible. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"A standardized field would allow ecosystem-wide compliance" - what? This is nonsensical. Wallets store their data in non-standardized formats.