Only network tokens appear automatically on most networks. This guide outlines the steps for importing the rest of the tokens supported on Nume.

Nume supports 5 other tokens besides its network token, DAI, at launch: USDT, USDC, MATIC, WBTC, and ETH. Note: Token onboarding will eventually be permissionless.

Here are the token contract addresses:

• USDC: 0xA8CE8aee21bC2A48a5EF670afCc9274C7bbbC035
• USDT: 0x1E4a5963aBFD975d8c9021ce480b42188849D41d
• WBTC: 0xEA034fb02eB1808C2cc3adbC15f447B93CbE08e1
• MATIC: 0xa2036f0538221a77A3937F1379699f44945018d0
• ETH: 0x1111111111111111111111111111111111111111

Step-by-step guide on Import a token on Metamask

1. Click on ‘+ Import tokens’

2. Enter the token’s contract address (shared in the previous section above).

3. Here, we are importing in ETH.

4. Next, click Import

5. The token has been imported!

6. View all your tokens in the Tokens section

7. Rinse and repeat

Unlike other networks, withdrawals from the Nume network cost a flat 0.10 DAI. With a Nume Premium subscription, withdrawals are fee-less.

Here’s your step-by-step guide to withdrawing from Nume Mainnet back to Polygon zkEVM.

1. Before getting started, make sure you have sufficient DAI for withdrawals which are a flat 0.10 DAI.

2. Select the token to withdraw from the Token dropdown and enter the amount.

3. Review the withdrawal.

4. Approve the transaction on Metamask.

5. Your withdrawal request has been initiated and will be processed as part of Nume’s next settlement.

6. Navigate to the latest block on Nume’s Block Explorer page to view your transaction: https://explorer.numecrypto.com/

7. Back on the bridge website, note that the DAI balance has a 0.10 DAI deduction.

8. Navigate to ‘Transaction History’ to check the latest status of your withdrawal. Once the block which contains your withdrawal has been finalized on Polygon zkEVM, the status will change from ‘Processing’ to ‘Complete’.

9. The withdrawal has been finalized on zkEVM. Click on claim funds to transfer funds from Nume’s contract on Polygon zkEVM to your wallet.

10. Sign the request on Metamask

11. Review the transaction on Metamask and Click Confirm

12. Funds have been claimed successfully.

Nume Premium is the first rollup subscription model on Ethereum, deployed on zkEVM. For 1.99 DAI per month, subscribers can unlock unlimited fee-less operations on the network which include token transfers, withdrawals, NFT transfers, mints, and trades. Learn more

This guide will walk you through the simple process of subscribing to Nume Premium.

Before getting started, make sure that you have sufficient DAI to cover a Nume Premium Subscription — 1.99 DAI. If not, bridge funds in from Polygon zkEVM to the Nume network.

1. Navigate to the Premium page.

2. Subscriptions are recurring on a monthly cadence unless canceled. Nume Premium is a trustless subscription model meaning you don’t have to rely on our Sequencer to cancel your subscription, you can directly cancel via our protocol if you choose to. Click on ‘Confirm’.

3. Provide your signature to provide approval for the Nume contract to withdraw 1.99 DAI on a recurring basis.

4. Your subscription is now active! Cancel anytime by clicking on ‘Cancel Subscription’

5. Note that the ‘Active’ badge will appear once you refresh the page. Your DAI balance has been deducted towards your Nume Premium subscription.

6. With an active Nume Premium subscriptions, token transfers (usually 0.05 DAI) and withdrawals (0.10 DAI)become fee-less. As do NFT mints, transfers and trades!

Sending money on the Nume network is instant with a flat fee of 0.05 DAI. This guide outlines the process of conducting a P2P transfer on Nume Mainnet.

Before getting started, make sure you have completed these steps:

1. Add the Nume network to your EVM wallet.
2. Bridge in funds from Polygon zkEVM into Nume Mainnet.
3. Ensure your tokens are showing up in your EVM wallet.

Note: To bridge or send funds on the Nume network, you and the recipient(s) will need to have agreed to Terms and Services and Privacy Policy on the Nume Bridge site.

Step-by-step guide on Metamask

1. In the network selector, select Nume Mainnet.

2. Click on Send.

Note: You may see a red error icon next to DAI. Clicking on this message will say “This network doesn’t match its associated chain ID or name…” This will be removed soon and does not impact any functionality.

3. Enter the recipient’s address.

Note: Most EVM wallets expect gas fees to be a parameter, hence you will see incorrect ‘Gas’ displayed. Nume will only charge flat fees of 0.05 DAI on transfers. You will see this accurately reflected in your DAI balance post-transfer.

4. Confirm the transaction. Again, ignore any gas calculated.

Congratulations! You’ve successfully completed your first P2P transaction on Nume 🎉

5. Back in the Balance section, note that a flat 0.05 DAI was deducted on the transfer. The previous balance of 1 DAI is now 0.95 DAI.

6. Visit bridge.numecrypto.com to see your Balance breakdown and…

7. Navigate to Transaction History to see all your activity on the Nume network.

This guide will walk you through the simple process of bridging your assets into Nume.

Note: Before getting started make sure you have funds on Polygon zkEVM to bridge in! DAI is Nume’s network token and needed to pay the network’s flat fees.

Navigate to the Bridge tab in the Nume Bridging Website and connect your wallet.

2. You’ll be prompted to connect to the Polygon zkEVM network if it’s not active. View all available tokens under the Token dropdown. Select the token you want to bridge in and enter the amount

3. Approve a spending cap. This ensures Nume’s contract cannot access more money than the limit set.

4. Confirm the transfer

5. Bridging usually takes less than 30 seconds

6. See the updated balance almost immediately.

7. Follow the same steps to bridge in any supported token to the Nume network from Polygon zkEVM: WBTC, ETH, USDC, MATIC, USDT, DAI.

There are two ways to setup the Nume network on your EVM wallet: 1) Through the Nume Bridge (recommended) 2) Adding the Nume Mainnet network manually to your wallet.

Note: To bridge or send funds on the Nume network, you and the recipient(s) will need to have agreed to Terms and Services and Privacy Policy on the Nume Bridge site.

1. Connecting to the Nume Network from the Nume Bridge

1. Connect your wallet at https://bridge.numecrypto.com/

2. Review and accept Nume’s T&S and Privacy Policy.

3. Click the ‘Add Nume Network’ button (top right)

Congratulations, you are setup with the Nume Network! 🎉

2. Adding the Nume Network manually

Network details:

• Network Name: Nume Mainnet
• RPC URL: https://rpc.numecrypto.com
• Chain ID: 7100
• Currency Symbol: DAI
• Block Explorer URL: https://explorer.numecrypto.com/

Note: To bridge or send funds on the Nume Network, you and the recipient(s) will need to have agreed to Terms and Services and Privacy Policy on the Nume Bridge site.

Step-by-step guide on Metamask

1. Select the network switcher

2. Click on Add network

3. Select Custom Networks

4. Add Network details

• Network Name: Nume Mainnet
• New RPC URL: https://rpc.numecrypto.com
• Chain ID: 7100
• Currency Symbol: DAI
• Block Explorer URL: https://explorer.numecrypto.com/

5. Balance view

Step-by-step guide on Coinbase Wallet

1. To add a network on the Coinbase wallet, go to Settings and click on Networks

2. Click on the + icon on the top right

3. Enter network details and click on ‘Add network’

4. Make sure that the network has been added in the ‘Custom’ tab

A New Chapter in Blockchain Accessibility

We at Nume Crypto are thrilled to announce the launch of Nume Premium, a pioneering subscription service that represents a significant milestone for the Nume protocol and the broader blockchain community. Nume Premium offers unlimited access to all protocol operations under a single, easy-to-understand pricing structure. As it is, the Nume network is priced in DAI and has no concept of gasprice or congestion, which means that users can engage with the sercice without worrying about fluctuating costs or complex fee structures. However, we want to further eliminate the cognitive burden of even factoring in a per-operation fee every time users interact with the protocol. We are hence introducing Nume Premium, which allows users to access all protocol operations for *no* additional fees apart from the subscription charge billed (approximately) monthly. Our goal is to make blockchain technology more accessible, and Nume Premium is a significant step in this direction.

Empowering Users with Trustless Cancellation

A core tenet of Nume Premium is its trustless nature. The subscription service is enshrined into the network; this means that the subscription status of a user is tracked in the network state tree and users can cancel their subscription at any time without depending on our Sequencer to process the request. This trustless cancellation is facilitated by the user’s direct interaction with Nume’s bridging contract on Polygon zkEVM, whereby they can prove that they are a subscribed user and submit a cancellation request that is enforced by the contract. Of course, users will have an easier experience submitting a cancellation request with our Sequencer at bridge.numecrypto.com. Note: the subscription amount and frequency are values currently set by us and these parameters will soon be enshrined in the protocol as well.

Seamless Subscription Process

Subscribing to Nume Premium is easy. Users can sign up through the Nume bridging website at bridge.numecrypto.com. Once subscribed, the Nume network automates the billing process, deducting the subscription fee from the user’s Nume balance every X settlements. The cadence of settlements will be fine tuned over time based on network traffic. To ensure that subscribers are billed no earlier than 30 days, subscriptions will initially be setup to renew at the uppermost bound of frequency of settlements. This number will be updated to most accurately match a month over time.

To celebrate the launch of Nume Premium, we are offering an introductory price of just $1.99 DAI per month. This special rate is our way of thanking our early adopters and making Nume Premium accessible to a broader audience.

Looking Forward

With Nume Premium, we are not just launching a subscription service; we are redefining how users interact with blockchain protocols. Our mission has always been to drive innovation and inclusivity in the blockchain space, and Nume Premium is a testament to this commitment. We invite you to join us on this exciting journey and experience the full potential of the Nume protocol.

Stay connected with us for more updates and exciting developments in the world of blockchain and cryptocurrency.

Explore Nume Premium today and be part of the blockchain revolution!

The Nume Protocol will launch as a Layer-3 on Polygon zkEVM. However, until support for necessary precompiles is introduced, we will operate on the Polygon PoS chain starting Q3 2023.

The Nume protocol is a new type of rollup deployed on Ethereum that provides trustless instant settlements without the computational overhead of zero-knowledge proofs. Where existing rollups navigate a tradeoff between cost and settlement finality times (i.e. Optimistic Rollups vs Zero Knowledge Rollups), we mitigate the tradeoff by utilizing hardware enclaves and decentralized governance. For an overview, please refer to this post.

We previously discussed Nume’s Security Model and in this post, we will discuss the Nume Protocol’s data availability (DA) model.

Guaranteeing data availability on IPFS

Nume stores transaction data corresponding to each settlement in IPFS. Each run of the hardware enclave (which executes the offchain rollup algorithm to compute the new state) starts by the enclave first downloading the transaction data from a provided IPFS CID. The content is downloaded from IPFS over https and the enclave performs a TLS handshake to verify the integrity of this data. This downloaded content becomes the basis for the state transitions in this settlement, and the CID is a part of the final commitment to the new state generated by the enclave.

Once the execution of the state update algorithm inside the enclave is completed, we submit the new generated commitment to the contract, hence making the CID location for the transactions processed public on the blockchain. This design guarantees that the transaction data behind a settlement is made publicly available. We use Pinata to pin these transaction documents on IPFS for atleast a month so that interested users have ample time to download them.

We would love to hear from you. Please reach out with any questions or feedback here or on Twitter!

The Nume Protocol will launch as a Layer-3 on Polygon zkEVM. However until support for necessary precompiles is introduced, we will operate on the Polygon PoS chain starting Q3 2023.

The Nume protocol is a new type of rollup that provides trustless instant settlements without the computational overhead of zero-knowledge proofs. For an overview, please refer to this post. In this blog, we’ll dig deeper into the security model, the limitations of the current implementation, and the roadmap to full trustlessness.

Software verification, not transaction verification

The Nume protocol involves an off-chain system that receives crypto transactions and generates periodic settlements and a set of on-chain contracts that validate settlements submitted to them. While rollups today are secured by on-chain verification of the off-chain transactions (e.g. via zero-knowledge proofs), the Nume protocol is a fundamentally different paradigm. With Nume, the on-chain contract verifies that the new state being settled has been generated by software that has been authorized. That is, given a “correct” rollup codebase (e.g. that would capture transaction validation rules, state tree update rules, etc) that the contract trusts, we need only have a hardware enclave (and no zk proof) that runs this codebase as long as we can prove that the output — the new state root — is generated from a run of this algorithm with the correct inputs (e.g. the correct previous state). The security of the system then rests on: 1) the mechanism for code authorization, and 2) the mechanism for verifying the integrity of a state update — that it is the result of executing the authorized code off-chain.

Authorizing a source update

Nume relies on the active participation of its community to upgrade its protocol. While it is typical for on-chain code to be upgraded via decentralized governance, this is the first time such a process is being applied to off-chain code (i.e. the component that executes inside the hardware enclave). Please note that a multisig will govern the protocol at launch and will be replaced by a DAO shortly afterwards.

To update the Nume protocol’s software (whether onchain or offchain), we will make improvement proposals and collect community feedback. The goal of this step is to settle directional debates. Once the implementation is ready, it will be available for anyone to review and provide feedback. Finally, we transparently generate a commitment to this updated software which anyone can verify the provenance for and put it up for community vote. If the vote passes, the update is automatically finalized onchain.

Finalizing updates to offchain software onchain

An obvious way to authorize the updated offchain software onchain is as follows. The contract stores a reference to the “correct” code that executes inside the enclave such as its hash. In every settlement thats processed, it looks for an attestation document that referneces this hash, thereby attesting to the fact that the new state provided was generated from this code. When there is an update to this offchain code that is affirmatively voted on, the onchain execution of the vote simply changes this reference value stored by the contract to whatever the new hash of the updated source is.

The key drawback with this approach is that such attestation documents generated by enclaves like AWS Nitro or Intel SGX are 1) computationally expensive to decode on-chain (on the order of millions of gas), and 2) verifying them requires verification of the entire chain of trust, meaning multiple signature verifications over a non-blockchain-friendly curve like P384 which further drives up the gas cost by several millions. This results in astronomical gas costs that we would then be forced to pass on to the user, which is exactly antithesis to our goal.

We’ve instead designed an upgrade progress that retains the security of on-chain attestation verification but at 100–200K gas per settlement. Instead of storing a reference to the offchain code, the contract instead stores a “settlement signer” address that it expects each new state update to be signed with. During a settlement verification, all it does is an ECDSA signature verification to check if the provided state has been signed by this address (along with a few other checks). This address is generated inside the hardware enclave; only the enclave knows the private key, and only the original codebase that generated it can ever access it. When an update to the offchain source is to proposed for governance, a attestation document is provided as part of the proposal that contains: 1) an secp256k1 address, 2) a unique reference to the code that was executed to produce this address. Anyone voting on the proposal can independently verify the following things:

• The source code (as of this update) yields the same reference value as seen in the attestation document
• The source code generates a secp256k1 key-pair that results in the same address as provided in the attestation document, and seals the private key as a secret that is decodable only by that exact same unmodified source
• In comparison with the last version, the source code contains updates to the rollup algorithm that they agree with
• The attestation document has been correctly signed and the chain of trust to a trusted root CA is verifiable

The checks above can be performed by anyone and ensures that by voting on the proposal, the governance committee only admits a settlement signer address to the contract that exactly and only corresponds to the source update that they would like to vote in.

In the next few blogs, we’ll cover Nume’s data availability model and how the Nume protocol lends itself to parallelized batch processing and hence horizontal scalability.

We would love to hear from you. Please reach out with any questions or feedback here or on Twitter!

The Nume Protocol will launch as a Layer-3 on Polygon zkEVM. However until support for necessary precompiles is introduced, we will operate on the Polygon PoS chain starting Q3 2023.

I’m Madhumitha Harishankar, CEO of Nume Crypto. Today, I’m excited to announce the testnet launch of the payments protocol that we’ve been building in stealth for over a year — the Nume Protocol. Nume disrupts existing scaling solutions in the Ethereum ecosystem by offering an entirely gas-abstracted infrastructure with a flat fee (taken in DAI) monetization model for all token and NFT activities, doing away with variable gasprice and percent fees. Let’s dive in.

We believe web3 will be brought to the masses on the most trusted, decentralized, and secure Layer-1 blockchain — Ethereum — notwithstanding its current scaling limitations. At 30TPS, variable and expensive gas costs are a deterrent even to early adopters and will be a massive barrier in onboarding the next billion into web3 — users who will not put up with confirmation delays, high gas fees, or even just variable fees.

The predominant approaches to trustlessly scaling Ethereum involve trading off between cost and settlement finality time, and the Nume protocol exists to bridge this gap. Our infrastructure scales supported operations without using zero-knowledge proofs while also providing instant settlement finality on-chain. Additionally, Nume can batch an unlimited number of transactions for a fixed on-chain commit cost, enabling dApps to hyper-scale and bring web2-like traffic to web3 at the lowest cost. Note that Nume will not support smart-contract deployment at launch— it will support asset transfers and specific predefined operations (defined by Nume). In this aspect, it’s similar to zkSync Lite or Loopring.

Existing Approaches

We provide a brief (simplistic) overview of Optimistic Rollups (OR) and Zero-knowledge Rollups (ZKR) before diving further into our protocol. With OR, a sequencer batches transactions and sends the compressed transaction data and new state commitment to the OR contract on Ethereum. A challenge-response (C-R) period now commences, allowing users/validators of the network to discover and prove incorrect state transitions in this new state before it is finalized on Ethereum. While ORs offer fast transaction confirmation times (off-chain) and incur low costs, this C-R period, which usually lasts 7 days, delays settlement finality significantly (and undesirably).

In ZKRs, similar to ORs, the sequencer batches multiple transactions and computes the new state transition. However, this time the sequencer (or a verifier) also generates a zero-knowledge proof that cryptographically proves the state transitions to the new commitment. This proof is sent to the rollup contract on Ethereum, which instantly accepts the new commitment if the proof verifies. The drawback, however, is the substantially high resource cost incurred to compute zk proofs, which typically results in a higher gas cost passed onto users (compared to ORs).

Nume’s Approach

At Nume, we mitigate this cost-finality tradeoff by combining hardware enclaves with decentralized governance. We execute the rollup algorithm (that verifies transactions and computes the new state) in a hardware enclave, also called Trusted Execution Environment (TEE). The new state generated at the end of the computation is attested by the TEE and one of the attested measurements is a reference to the source code itself. The on-chain contract is configured to accept new state commitments as long as it is accompanied by an attestation from the correct source code. But who decides the correct source code? This is where decentralized governance comes in — while multisigs and DAOs typically govern on-chain code, in Nume’s case they also govern the off-chain code that runs inside the TEE. Any modifications to the off-chain rollup algorithm must be voted on via on-chain governance for the contract to start accepting commitments with attestations that point to the modified source.

While we discuss further details in a separate post, it is important to highlight the efficiency of Nume’s model. Given an authorized source code, state commitments are instantly accepted by the on-chain contract as long as the conditions on the attested values pass. Then users only need to watch the contract for any proposed updates to the rollup software. They can verify an update (whether to the onchain or offchain protocol code) themselves during the cooling period that the contract enforces, and, if unconvinced by the governance outcome on the update, exit their funds. Either way, users do not need to watch the chain constantly to verify the validity of every single posted settlement, which is a big win in usability.

Since the Nume protocol proves the off-chain computation that was performed to the contract without any computationally expensive zk proofs, it also incurs much lower gas costs than ZKRs. It brings the power of centralized computing solutions to blockchain scaling in a trustless manner without the cost limitations of ZK proving or the usability limitation of long finality times. It also enables an entirely new security paradigm for accessing off-chain services and data on-chain; by embedding such access inside the rollup software that executes in the off-chain TEE, we can offer foundationally more secure oracles (and other services). A deep dive on Nume’s security model, limitations of its current implementation, and the roadmap to full trustlessness and decentralization is covered here.

We can’t wait to bring Nume to you in its closed mainnet beta in early Q3 2023. If you like to be in great company and want access to our beta, let’s chat. Our docs for testnet are available here. We would love to hear your feedback — if we can make development easier or optimize the stack for your particular use case, please reach out via Twitter. We’ll expand on our roadmap in a subsequent post. We are excited to dialogue with the community to inform our feature development roadmap so please reach out to chat! :)