For the complete documentation index, see llms.txt. This page is also available as Markdown.

RISE Testnet Deployment

Rise Testnet Deployment

We chose to deploy Canary Nest Oracle on the Rise Testnet to really highlight its top-tier performance. Rise stands out as the fastest blockchain available today, churning out 5-millisecond pre-confirmations known as shreds. By pairing our oracle with the quickest chain out there, we get to demonstrate just how blazingly fast and secure Canary can be in a real-world setup. Canary Nest is up and running on Rise Testnet, delivering 12-millisecond latency without any fancy tweaks, all over standard HTTPS. Throw in some optimisations like switching to websockets, and we can easily hit 1 millisecond. That makes Canary the fastest and most secure oracle on the planet, bar none. A quick look at the block explorer screenshot shows we managed over 80 updates in a single block, even without those optimizations. It proves our point: high throughput and low latency in action.

We ran a quick benchmark for Canary Nest Oracle on the Rise Testnet to show its speed and efficiency.

Here is how it all came together, step by step: Setup Details We used an Amazon Linux 2023 setup on an AWS EC2 c5. large instance with 2 vCPUs and 4 GB of RAM, located in Northern Virginia (us-east-1). The round-trip time to the Rise node clocked in at about 0.9 to 1.2 milliseconds. Our Go-compiled binary sent raw transactions via HTTPS JSON RPC, though we could shave off more latency with websockets. We broadcasted a sequence of 200 price rotations in quick succession to the Rise Testnet node.

The transaction signer was at 0x647dF90C3C2E63c992Bd44F8e334B7cCc2db3029, and the smart contract sat at 0xf3D0BE54D25D4E36434237833308414bC7aC6be2.

Benchmark Results : The whole run kicked off at 2025-07-20T16:08:30.523Z and wrapped up by 2025-07-20T16:08:33.005Z. That gave us a total duration of 2482 milliseconds, with an average latency of 12.41 milliseconds per transaction and a solid rate of 80.5 transactions per second.

No garbage collection pauses popped up, thanks to the short process lifetime. For a clearer breakdown of the average transaction latency, check out this table:

Component

Description

Latency (ms)

CPU-bound operations

Constructing calldata and signing the transaction

0.4

HTTP and SSL overhead

Network roundtrips and related delays

3.0

Remaining latency

Receiving response from eth_sendRawTransaction JSON RPC

9.0

This setup highlights how Canary Nest Oracle delivers fast, reliable performance even on testnets, making it a strong fit for real-world use.

Explorer data

You can check transaction history on the signer address: https://explorer.testnet.riselabs.xyz/address/0x647dF90C3C2E63c992Bd44F8e334B7cCc2db3029

Or logs on the smart contract https://explorer.testnet.riselabs.xyz/address/0xf3D0BE54D25D4E36434237833308414bC7aC6be2?tab=logs

Logs

Last updated