Difference between revisions of "Building on Bitcoin"
| Line 10: | Line 10: | ||
* [[Metanet Protocol]] - Defines a directed graph structure that stores data on the blockchain where that data can easily be queried and referenced by other applications. | * [[Metanet Protocol]] - Defines a directed graph structure that stores data on the blockchain where that data can easily be queried and referenced by other applications. | ||
* [https://www.tokenized.com Tokenized Protocol] - Defines protocol and platform where issuers and users can create, manage and trade tokens leveraging built-in smart contracts. | * [https://www.tokenized.com Tokenized Protocol] - Defines protocol and platform where issuers and users can create, manage and trade tokens leveraging built-in smart contracts. | ||
| − | * [https://github.com/unwriter/B B://], [https:// | + | * [https://github.com/unwriter/B B://], [https://c.bitdb.network/ C://], [https://planaria.network/@1G3BpTyEK6xF4LaQTHqdFBBaVxYHZzts4M D://], [http://bcat.bico.media/ BCAT] - Various protocols for storing files on-chain and referencing them in a web page or application. |
* [https://github.com/BitcoinFiles/AUTHOR_IDENTITY_PROTOCOL/ AIP - Author Identity Protocol] - Simple protocol to sign arbitrary OP_RETURN data and decouple the signing address from the funding source address. | * [https://github.com/BitcoinFiles/AUTHOR_IDENTITY_PROTOCOL/ AIP - Author Identity Protocol] - Simple protocol to sign arbitrary OP_RETURN data and decouple the signing address from the funding source address. | ||
* [https://github.com/rohenaz/MAP/ MAP - Magic Attribute Protocol] - Protocol that maps arbitrary data to key/value pairs on-chain. | * [https://github.com/rohenaz/MAP/ MAP - Magic Attribute Protocol] - Protocol that maps arbitrary data to key/value pairs on-chain. | ||
Revision as of 21:22, 14 December 2019
Here you can find information on and links to some of the tools developed for Bitcoin including:
- Neon Planaria - Javascript framework that generates a state machine and database as well as an API to interface other applications with.
- Bitbus - Creates a filtered subledger of Bitcoin transactions in your file system, bypassing the need for application developers to run a node.
- Moneybutton - Simple payment API where users swipe a button to generate a Bitcoin transaction for payment and/or write data to the blockchain.
- Cashport - API framework that enables developers to easily manage micro-payments for services in your application.
- Paymail - Protocol that defines how to send Bitcoin to a human readable, email like namespace instead of a Bitcoin address.
Widely used 2nd layer protocols:
- Metanet Protocol - Defines a directed graph structure that stores data on the blockchain where that data can easily be queried and referenced by other applications.
- Tokenized Protocol - Defines protocol and platform where issuers and users can create, manage and trade tokens leveraging built-in smart contracts.
- B://, C://, D://, BCAT - Various protocols for storing files on-chain and referencing them in a web page or application.
- AIP - Author Identity Protocol - Simple protocol to sign arbitrary OP_RETURN data and decouple the signing address from the funding source address.
- MAP - Magic Attribute Protocol - Protocol that maps arbitrary data to key/value pairs on-chain.
- Other second layer protocols (contact [email protected] to have your stable, released protocol added)
Decision needed: Break these out into their own pages or have one larger page with sections? Already have a page for SVAlias...