Adds the lokad id for dust tx authentications.
Usage:
<lokad> <utf8 identifier>
Details
Details
- Reviewers
bytesofman - Group Reviewers
Restricted Project - Commits
- rABCb05a734b5c0d: Add dust tx authentication prefix to standards doc
plonk into https://jbt.github.io/markdown-editor/ and proof read
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- authSpec
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 29976 Build 59486: Build Diff Build 59485: arc lint + arc unit
Event Timeline
Comment Actions
<utf8 unique identifier>
is there any expected byte length here? what makes it unique? what happens if someone starts broadcasting clones of these txs ... there's no way to guarantee this is unique since it is public.
Comment Actions
is there any expected byte length here? what makes it unique? what happens if someone starts broadcasting clones of these txs ... there's no way to guarantee this is unique since it is public.
As per tg discussion
Comment Actions
beyond the scope of this diff -- but why different lokad id for all of these things that are different functions of ecashchat?
it seems like these use cases are tailored specifically to ecash chat and not to generalized auth or generalized paywalls.
| doc/standards/op_return-prefix-guideline.md | ||
|---|---|---|
| 23 | ||
Comment Actions
beyond the scope of this diff -- but why different lokad id for all of these things that are different functions of ecashchat?
Both paywall and auth lokads are meant to be app-neutral, as there is no eCashChat specific data in the payload - e.g. with paywalls you'll always be paying for an article so including a txid to indicate what you're paying for is quite generic. Similarly with auth tx, various apps can decide what kind of identifier to use and is not specific to eCashChat.