PayButton is looking for a standardized way to encode certain data into OP_RETURN fields to increase app functionality.
Details
Details
- Reviewers
Klakurka - Group Reviewers
Restricted Project - Commits
- rABC8ccd30345bab: [standards] Add spec for PayButton txs
Read and comment. Let me know if I am missing some intended use, or if there is some current use case that this spec would miss.
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
Display Name: PayButton
Authors: Blockchain Ventures
Address: ecash:qrmm7edwuj4jf7tnvygjyztyy0a0qxvl7quss2vxek
doc/standards/paybutton.md | ||
---|---|---|
36 ↗ | (On Diff #44221) | What about adding a bit to this to clarify the padding (same with line 49)? 50415900 - PayButton protocol identifier, ascii "PAY" padded on the right with a 0 byte ? |