-
This suggestion directly contradicts issue #41 and PR #43.
If this suggestion were implemented it would simplify and/or reduce the "urgency" and/or criticality of #44, #45 and #46.
Suggestion …
-
These all came from my comments as TODOs and I want to enumerate them here. We should make sure the spec _clearly makes the following points_ (if it doesn't already):
- **Standardness changes**. Ca…
-
The [`Shared Codepoint for All Tokens`](https://github.com/bitjson/cashtokens/tree/f8b500a051f82d42dbf9e9e890bc6cdc14592307#shared-codepoint-for-all-tokens) rationale was written for a pre-release ite…
-
I suggest this in conjunction with #47 .
This idea came up as part of discussion in #41 here: https://github.com/bitjson/cashtokens/issues/41#issuecomment-1193352610
Note that if we move the cap…
-
Proposed specification for the format, implements everything talked about in https://github.com/bitjson/cashtokens/issues/27 https://github.com/bitjson/cashtokens/issues/25 https://github.com/bitjson/…
-
@zander brought up that a two-stage activation might allow us to clean up any "pre-activation token-forgery outputs" before tokens are activated, e.g.:
At block `N`, outputs beginning with `PREFIX…
-
I've had a chat with Calin, the length limit should be independent of Script length instead of eating into the Script limit with token data, much less mess, and 520 is a sane limit since anything abov…
-
From https://github.com/bitjson/cashtokens/issues/24#issuecomment-1179224180
>E.g. even if we had a simple OP_OUTPUT_TOKEN_CAPABILITY that accepted an index and returned one of these above numbers …
-
@thesquaregroot identified an ambiguity in the spec we need to be sure is handled explicitly: any locking bytecode can begin with `0xd0` (`OP_UTXOTOKENAMOUNT`), even for outputs that do not themselves…
-
Summary of Suggestion
---
I suggest we kill two birds with one stone and just change the prefix to `bch:` for mainnet ~~and `tbch:` for testnets and scalenet~~. ~~Perhaps also `rbch:` for regtes…