Building on Bitcoin

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.
Datapay - Simple JS library that enables broadcasting of Bitcoin transactions with as little as 4 lines of code.
Moneybutton - Robust 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 and implement 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.
Bitcom - Decentralized registry of application protocols, uniquely identified by an input address, proving ownership. Bitcom protocols can be concatenated together with a | character.
B://, C://, D://, BCAT - Various protocols for storing files on-chain and details how to reference 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 via key/value pairs on-chain.
HAIP - Hash Author Identity Protocol - Similar to AIP but hashes the data signed for smaller capacity devices.
Contact Brendan Lee at [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...