
https://xitter.cf/t.co/TQtvYXjDsh | Leading DLT service provider. Building @BoltRPC. Join our Telegram group: https://xitter.cf/t.co/NVB8SCT5PQ
Chainlink Network
Joined February 2021
- Tweets832
- Following194
- Followers679
- Likes1.6K
Heimdall v0.12.2 from @0xPolygon lets a node recover from a late upgrade by itself. A node that ran an old binary past a hardfork height re-runs its last block on restart.
Until now that took a manual rollback. Our validator runs v0.12.2.
Delegators need not do anything.
Prysm v7.3.0 from @prylabs schedules the Gloas fork on Ethereum's Hoodi testnet for 26 October. Hoodi operators need to update beacon nodes and validator clients before then.
Mainnet gets fixes in this release too, and Prysm recommends updating beacon nodes there.
Glamsterdam has been live on Sepolia since 6 Oct. Hoodi: 26 Oct. Mainnet has no date yet.
A headline change is enshrined proposer-builder separation (EIP-7732): the builder's payment to the proposer moves into @ethereum's consensus.
Validators get new duties to prepare for.
On @iota, staked tokens earn only for epochs they are active for in full. Stake today and it counts from the next epoch. Epochs last 24 hours.
Withdraw whenever you like: principal and rewards come back together.
Unstaking mid-epoch means that epoch doesn't earn.
Fort Canning, Enjin Relaychain runtime v1.8.0, is set for 9 Nov at block #18,059,100 if its referendum passes.
It brings dispute slashing to @enjin: validators that back or approve an invalid candidate lose stake, and so do their nominators.
Validators need client v1.8.0.
Chainlink node v2.67.0 from @chainlink adds Postgres 18. Since v2.66.0 the minimum is 15. Releases ship about weekly.
Every release image is signed, so an operator can verify it with cosign against the published digest before it runs.
Protocols reading a feed see none of this.
Lugano from @0xPolygon activated at Heimdall block 54,627,000 on 1 Oct: this hardfork is set by a Heimdall height.
Nodes on v0.11.0 or older ran past it under the old rules and halted. An upgrade alone didn't fix them.
That is why validators upgrade first.
IOTA mainnet has run protocol version 37 since epoch 521, which began on 8 Oct at 07:42 UTC. It shipped in v1.33.1 from @iota.
Version 37 rejects a transaction naming an object version reserved for canceled ones, before any object loads.
Our validator runs v1.33.1.
A @chainlink price feed update is one transaction, not one per node.
Operators sign observations off-chain, an elected leader aggregates them, and a quorum signs the report. The contract checks the signatures and serves the median.
No single node sets the price. That's OCR.
The full walk-through, from each operator's own sources to the one on-chain answer: matrixed.link/blog/what-is-a…
An oracle update that makes a loan liquidatable starts a race. The fastest bot takes the liquidation bonus.
@chainlink SVR auctions the right to backrun that update. The winning bid is split between the lending protocol and the Chainlink Network.
How SVR works, step by step: matrixed.link/blog/chainlink…
A @chainlink price feed does not update every block. Two triggers decide.
Deviation: the price moves past a threshold. Heartbeat: a set time passes with no update.
ETH / USD on Ethereum: 0.5% or 3600s. If updatedAt is older than the heartbeat, treat the price as stale.
Blockchain RPC and Blockchain Node Engine shut down on 15 Dec, per @googlecloud.
Moving is an endpoint swap. Same Ethereum JSON-RPC, new URL.
BoltRPC serves Ethereum mainnet, Sepolia and Hoodi, plus beacon endpoints. One key, 36 chains.
Swap the URL and test before 15 Dec.
A reserve audit is a snapshot. @chainlink Proof of Reserve is the live layer in between.
Oracle nodes read reserve data, agree on it and post it on-chain. A minting contract can read that feed and refuse to mint beyond the reserves.
matrixed.link/blog/chainlink…
Third chain in our synthetic WebSocket series: @SuiNetwork.
Sui produces checkpoints faster than most infrastructure can keep up with. That is a compliment to the chain, and a genuine engineering problem for anyone reading it.
Sui nodes do not offer a WebSocket, so polling is the default answer. On a chain this fast, polling means you learn what changed after the fact and miss whatever happened in between.
So we push instead. The latest checkpoint reaches you the moment it lands, streamed from our own proxy.
The full Sui read surface is there for your queries, without the unsafe methods that build transactions for you server side. Your keys stay yours.
Behind it sit multiple Sui nodes with automatic failover. If one drops, your stream keeps running.
Robinhood Chain is live on BoltRPC. @RobinhoodCrypto's Arbitrum L2 for tokenized stocks, built for 24/7 trading.
Settles to Ethereum via blob data availability, ETH for gas, ~100 ms preconfirmations. Uniswap and Chainlink live from day one.
boltrpc.io
Replying to @build_on_bob
@build_on_bob update: op-reth v2.4.4 and op-node v1.19.7 are now live on our BOB mainnet endpoint.
op-reth adds canonical-head basefee and gas-used metrics, matching op-geth. op-node ships a dependency cleanup, no runtime change.
No action needed on your side.
Replying to @katana
@katana on BoltRPC is current on conduit-op-reth v2.2.2.
This is a node-client bump, not a Katana hard fork. @conduitxyz published v2.2.2 on Sept 3. We applied it across our mainnet fleet today.
RPC's are synced and serving traffic.
Sign up and learn more here ➡️ boltrpc.io/networks/katana
Replying to @monad
@monad MIP-8 Phase C is complete on BoltRPC.
After the Sept 2 hard fork, we decommissioned the legacy slot-encoded TrieDB. Our mainnet nodes are now page-storage only; synced and serving as usual.
Details + trial → boltrpc.io/networks/monad


















