This repository has been archived by the owner on Sep 24, 2019. It is now read-only.
rfc fork #2
Merged
rfc fork #2
Conversation
This file contains 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
This BIP defines a new color kernel for transaction-based coloring. SPOBC colored coins are undivisible and require no padding. Since there can be only one unit, the satoshi value is not relevant. Smart property coins have a current position and a optional value. The current position is unspent outpoint containing the color. The value is up to 40 bytes of OP_RETURN data contained in the transaction associated with the current position.
This BIP defines a new color kernel for transaction-based coloring. DHKEC colored coins function like EPOBC, but have a method for deriving new addresses for dividend payment which keeps dividends seperate from the colored tokens.
Remove section on genesis output. That information will be communicated via a different channel. Clarify notation and indicate the shared secret is a sha256 hash Add reference to stealth address documentation from unSYSTEM
Define base58check standards for currently-defined color kernels to make color definitions more usable for URLs and other systems that use base58-encoded asset identifiers.
Add JSON schema, example data, and test script for outputlist
Add JSON schema, example data, and test script for withdrawalstatuslist
Add JSON schema, example data, and test script for outbailmentid
Add JSON schema, example data, and test script for siglist
"outpoints" is a more accurate description than "transactions"
Merge WIP rfcs
Turn schematest.py into a proper unit test
Remove .travis.yaml as we're using jenkins for CI
This specification allows a multiple-identity Bitmessage client to derive all needed keypairs from a single seed, which may be the same seed used to derive Bitcoin keypairs without the possibility of collision, greatly simplifying backup requirements and improving the user experience.
HD derivation of Bitmessage addresses
Schema and example json for signature status response to updateWithdrawal voting pool wallet API call.
Add a "required" field to siglist so that a seperate json schema is not needed for updatewithdrawal
Signature status
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
No description provided.