{"id":3891,"date":"2020-04-03T10:54:27","date_gmt":"2020-04-03T10:54:27","guid":{"rendered":"https:\/\/bitcoinsv.io\/?p=3891"},"modified":"2020-09-28T10:14:38","modified_gmt":"2020-09-28T10:14:38","slug":"miner-id-and-merchant-api-beta-release","status":"publish","type":"post","link":"https:\/\/bitcoinsv.io\/2020\/04\/03\/miner-id-and-merchant-api-beta-release\/","title":{"rendered":"Miner ID and Merchant API beta release"},"content":{"rendered":"\n
Background<\/strong><\/p>\n\n\n\n As the Bitcoin SV network continues its evolution toward the structural model described by Satoshi Nakamoto, new tools are emerging to support that change.\u00a0 As a part of the drive toward a safer instant transaction paradigm, the Miner ID and Merchant API projects have been discussed extensively. These projects have been in private beta testing and are now being released as a public beta and entering a public review process in the form of an RFC release.<\/p>\n\n\n\n Merchant API provides two critical services to enable application and wallet developers to use the Bitcoin network more efficiently:<\/p>\n\n\n\n Miner ID is a mechanism for miners to securely take ownership of their identity and reputation backed by their own proof of work.\u00a0 It has many applications beyond the initial use cases presented in our first version and is designed to be extensible. Initial use cases for Miner ID include:<\/p>\n\n\n\n It is intended that standards for both Merchant API and Miner ID will be passed through the Bitcoin Association\u2019 Technical Standards Committee (TSC) process, as soon as that is up and running.\u00a0 For expediency though, the proposed standards are being released now for public review. Both API standards are on Github and we request that feedback be directed through the Github issue system.<\/p>\n\n\n\n The draft specifications are in BRFC format<\/a> and can be found here:<\/p>\n\n\n\n The `misc` repository is for common specifications that have use cases outside of Merchant API and Miner ID.\u00a0 For example the fee spec standard will be proposed for adoption as a general standard for describing fees and will likely be proposed to be used in BIP270. To offer feedback, please use the Github issue system for the respective standard repositories.<\/p>\n\n\n\n Reference implementations can be found here:<\/p>\n\n\n\n For application developers that would like to test against the Merchant API a test instance is currently available.<\/p>\n\n\n\n MAPI: https:\/\/galt.bitcoinscaling.io:9004\/mapi\/feeQuote<\/a><\/p>\n\n\n\n Block explorer: https:\/\/stn.whatsonchain.com\/<\/a><\/p>\n\n\n\n Faucet: : https:\/\/faucet.bitcoinscaling.io\/<\/a><\/p>\n\n\n\n Mempool<\/a> have made available a mainnet instance of Merchant API for developer testing.<\/p>\n\n\n\n Documentation: https:\/\/developers.dotwallet.com\/en\/dev\/api\/merchant<\/a><\/p>\n\n\n\n
<\/p>\n\n\n\nServices<\/h2>\n\n\n\n
Merchant API<\/h3>\n\n\n\n
Miner ID<\/h3>\n\n\n\n
<\/p>\n\n\n\nRFC phase<\/h2>\n\n\n\n
<\/p>\n\n\n\nSpecifications<\/h2>\n\n\n\n
<\/p>\n\n\n\nReference implementations<\/h2>\n\n\n\n
Endpoints<\/h2>\n\n\n\n
Scaling test network<\/h3>\n\n\n\n
Mainnet<\/h3>\n\n\n\n