Merge pull request #75 from boo-0x/main

Add Reef chain

reef/README.md

@@ -0,0 +1,30 @@
+---
+namespace-identifier: reef
+title: Reef Namespace
+author: Boo 0x (@boo-0x)
+discussions-to: https://github.com/ChainAgnostic/namespaces/issues/74
+status: Draft
+type: Informational
+created: 2023-06-29
+---
+
+# Namespace Reef chains
+
+## Introduction
+
+Reef is a modular layer 1 blockchain for DeFi, NFTs and gaming. It is built with Substrate modules, has EVM support and uses Nominated Proof of Stake consensus. 
+Despite some tooling in common (such as [SS58][]-based per-chain addresses), direct interaction with Polkadot nodes, contracts, or wallets according to the standards of the Polkadot namespace is not currently possible.
+
+## Syntax
+
+The namespace "reef" refers to the Reef open-source blockchain platform.
+
+## References
+
+- [Reef Chain](https://reef.io/)
+- [Docs](https://docs.reef.io/)
+- [GitHub](https://github.com/reef-chain)
+
+## Copyright
+
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).

reef/caip2.md

@@ -0,0 +1,77 @@
+---
+namespace-identifier: reef-caip2
+title: Reef Namespace - Chains
+author: Boo 0x (@boo-0x)
+discussions-to: https://github.com/ChainAgnostic/namespaces/issues/74
+status: Draft
+type: Standard
+created: 2023-06-30
+requires: CAIP-2
+---
+
+# CAIP-2
+
+*For context, see the [CAIP-2][] specification.*
+
+## Rationale
+
+The namespace is called "reef" to encompass all chains of the Reef ecosystem. This includes a production network and one or more test networks.
+
+The rationale behind the use of block hash from the genesis block stems from its usage in the Reef architecture to secure network consensus.
+
+## Syntax
+
+The definition for this namespace will use the `genesis-hash` as an identifier for different Reef chains.
+The format is a 32 character-long lowercase hexadecimal string, **without** the `0x` prefix, representing the first half of hash of the 0 block (genesis block) for a given chain.
+
+As [CAIP-2][] references for this namespace are 32-byte hashes in lowercase hexadecimal, they can be validated with the simple regular expression: `[0-9a-f]{32}`
+
+### Resolution Method
+
+There is no index or registry that maps genesis hashes to networks, and defining such a mechanism for doing so is out of the scope for this specification.
+This specification assumes that consumers of this class of CAIP-2 identifiers are able to properly resolve them to the appropriate network.
+This specification then defines how to verify that a given RPC node, reachable via a regular URL, belongs to a given Reef network.
+
+Given the URL of a Reef network RPC node, make a JSON-RPC request to the node with method `chain_getBlockHash`, for example:
+
+```jsonc
+// Request
+{
+  "id": 1,
+  "jsonrpc": "2.0",
+  "method": "chain_getBlockHash",
+  "params": [0]
+}
+
+// Response
+{
+  "id": 1,
+  "jsonrpc": "2.0",
+  "result": "0x7834781d38e4798d548e34ec947d19deea29df148a7bf32484b7b24dacf8d4b7"
+}
+```
+The response will return as a result the hash of the block with height 0 (i.e., the genesis block).
+The leading `0x` and the last 32 characters will need to be trimmed, such that the resulting string is a 32-character Hexadecimal string (i.e., 16 bytes) that represents the Reef network in which the RPC node participates.
+
+## Test Cases
+
+This is a list of manually composed examples:
+
+```
+# Reef Mainnet
+reef:7834781d38e4798d548e34ec947d19de
+
+# Reef Scuba testnet
+reef:b414a8602b2251fa538d38a932239150
+     
+## References
+
+- [Reef Chain](https://reef.io/)
+- [Docs](https://docs.reef.io/)
+- [GitHub](https://github.com/reef-chain)
+
+[CAIP-2]: https://chainagnostic.org/CAIPs/caip-2
+
+## Copyright
+
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).