See More CryptosHome

RPC

Plutonians

Show Trading View Graph

Mentions (24Hr)

0

-100.00% Today

Reddit Posts

r/SatoshiStreetBetsSee Post

Andrew Kang is on fire; POKT surges another 20% after a single tweet by Kang. Pocket Network, a decentralized Web3 infrastructure provider, announced yesterday a major shift by expanding its services from only RPC data to serving indexing, AI, and any other open-source databases.

r/CryptoMarketsSee Post

Decentralized Web3 infrastructure provider Pocket Network has announced major shift by further expanding its service from RPC data to serving indexing, AI, LLMs and any other open source database.

r/SatoshiStreetBetsSee Post

Introducing The X Network. CruxDecussata $X

r/CryptoMoonShotsSee Post

Introducing The X Network. CruxDecussata $X

r/BitcoinSee Post

Alveychain

r/BitcoinSee Post

I wrote a Chain Code, mainly usable... I'm still working on

r/CryptoMarketsSee Post

XRPL EVM is launching in less than two weeks. POKT is rumored to be Ripple's chosen decentralized RPC provider to ensure seamless cross-chain transfers.

r/CryptoCurrencySee Post

Exploring Pokt Network and DePin

r/CryptoCurrencySee Post

POKT Network and DePin

r/CryptoMoonShotsSee Post

Alvey - When someone tells you that even a small investment in this could change You Life With One Simple Purchase Would You?!

r/CryptoMoonShotsSee Post

Alvey - If you’re looking for a trusted project, a real team and a REAL business plan. Give one minute of your time with this message!

r/CryptoCurrencySee Post

With Bitcoin transaction fees rising and there still being shiny new rug pulls on an almost weekly basis, why don't OG projects like Litecoin and DigiByte get more attention and appreciation?

r/SatoshiStreetBetsSee Post

Infura has just announced Microsoft and Pocket Network as their main partners on the road to decentralize RPC layer of the Web3 blockchain infrastructure.

r/CryptoMarketsSee Post

Coingecko's Top 8 centralized and decentralized RPC providers for blockchain communication. Infura and its decentralized RPC partner Pocket Network joined forces to secure unstoppable and permissionless RPC access to Web3 blockchain infrastructure.

r/CryptoCurrencySee Post

How to swap/convert/sell TOMO?

r/SatoshiStreetBetsSee Post

Infura partnered with Pocket Network as their main decentralized RPC provider. All of the Uniswap transactions happening through MetaMask will soon use Pocket Network and its protocol.

r/CryptoMarketsSee Post

Aave and Infura partnered with Pocket Network as their primary decentralized RPC provider. All of the Uniswap transactions happening through MetaMask will soon use Pocket Network.

r/BitcoinSee Post

Here is a Python code snippet that interacts with Bitcoin Core using the bitcoinrpc library. This allows you to send RPC commands to a running Bitcoin Core instance. You need to have bitcoinrpc installed to use this code

r/SatoshiStreetBetsSee Post

Massive bullish divergence on the weekly $POKT. Partnership between Infura, centralized RPC giant, and Pocket Network, leading decentralized RPC provider, is on the horizon!

r/SatoshiStreetBetsSee Post

Olimpio Crypto on X has strengthened rumors that Infura will decentralize its RPC layer using POKT Network

r/CryptoCurrencySee Post

Olimpio Crypto on X has strengthened rumors that Infura will decentralize its RPC layer using POKT Network

r/CryptoMarketsSee Post

The POKT DAO has opened its most important vote to date to expand support for any open-source service, in addition to existing RPC access. The implementation is complete and ready for release on the mainnet.

r/CryptoMarketsSee Post

POKT has partnered with Scroll ZKP to support Scroll Mainnet launch. Users can now access Scroll reliably using decentralized POKT RPC.

r/CryptoCurrencySee Post

“Don’t invest what you can’t afford to lose” - A reality that we must all consider.

r/CryptoCurrencySee Post

We all say “Don’t invest more the. You can afford to lose” now those who bought MOONS previously have to evaluate their risk factor.

r/SatoshiStreetBetsSee Post

The next big hype in the upcoming bull market will be Decentralized Physical Infrastructure Networks (DePIN). Keep an eye on high-revenue RPC protocols that can link up with real-world businesses - they're the ones likely to make the biggest gains in the 2024/2025 crypto bull run.

r/CryptoMarketsSee Post

The next big hype in the upcoming bull market will be Decentralized Physical Infrastructure Networks (DePIN). Keep an eye on high-revenue RPC protocols that can link up with real-world businesses - they're the ones likely to make the biggest gains in the 2024/2025 crypto bull run.

r/CryptoCurrencySee Post

Recap On ETH and ETHW

r/CryptoCurrencySee Post

POKT will launch its next-gen protocol as a Micro-Rollup using Rollkit's modular framework and Celestia as a Data Availability layer

r/SatoshiStreetBetsSee Post

Pocket Network has made significant progress toward decentralizing demand by launching an open-source gateway, funded by the POKT DAO, for its RPC protocol.

r/CryptoMarketsSee Post

Pocket Network has made significant progress toward decentralizing demand by launching an open-source gateway, funded by the POKT DAO, for its RPC protocol.

r/CryptoCurrencySee Post

Introducing the Maximal Extractable Value (or what we all know as MEV Bots)

r/CryptoCurrencySee Post

Saga: The Multichain Gaming Hub and it’s Shared Security Solution

r/CryptoMoonShotsSee Post

Empowering Web3 Builders Through DIA's Ultimate Builder Hub

r/CryptoMoonShotsSee Post

$ZOCI | CoinGecko Listed | Huge Marketing Plans | Start building Web3

r/CryptoMoonShotsSee Post

ZOCI - Start building Web3 | Listed on CG | Active Community | Security and Privacy features

r/CryptoMarketsSee Post

Pocket Network unveils strategic roadmap to unlock the full potential of the world's first decentralized RPC blockchain infrastructure

r/CryptoCurrencySee Post

What can you do about sandwich attacks and MEV bots? In response to jaredfromsubway.eth MEV bot stealing your hard earned eth.

r/CryptoCurrencySee Post

Can someone explain Shibarium?

r/CryptoCurrenciesSee Post

Solana's Transactions Unmasked: Going Beyond the Numbers

r/CryptoMarketsSee Post

Solana's Transactions Unmasked: Going Beyond the Numbers

r/CryptoCurrencySee Post

Solana's Transactions Unmasked: Going Beyond the Numbers

r/CryptoCurrencySee Post

[SERIOUS] Avoid MEV Bot Sandwitch Effect in ETH

r/BitcoinSee Post

JoinMarket v0.9.10: RBF fee bumping, drop Python 3.6, RPC API improvements, bugfixes

r/CryptoCurrencySee Post

The state of centralization of BTC/XMR hashrate

r/CryptoCurrencySee Post

Pool Centralization of BTC/XMR

r/CryptoCurrencySee Post

Sugar, fat, calories free donuts - u may want to give it a glance

r/CryptoCurrencySee Post

Introducing Transformers: A Revolutionary Blockchain

r/CryptoCurrencySee Post

Saga: The Multichain Gaming Hub and it’s Shared Security Solution

r/CryptoCurrencySee Post

SHIB, BONE, LEASH tokens dip amid rumors of $2.5M Shibarium gaffe

r/CryptoCurrencySee Post

Node Management Best Practices

r/CryptoCurrencySee Post

I want to post this extra bit of help I found when setting up Arbitrum Nova on metamask

r/CryptoCurrencySee Post

How to Vault > exchange, via metamask. - idiots guide.

r/CryptoCurrencySee Post

How to moons an idiots guide.

r/CryptoCurrencySee Post

What is the catch with DONUTS? the forgotten Community Points

r/BitcoinSee Post

Question: Public BTC Nodes

r/CryptoCurrencySee Post

The Complete Noob Guide for Trading MOONs

r/CryptoCurrencySee Post

Unknown error: "Internal JSON-RPC error."

r/CryptoCurrencySee Post

An Updated SUPER-Beginner’s Guide to Swapping, Bridging and Exchanging MOONs (the complicated way)

r/CryptoCurrencySee Post

[State of EVM] Ethereum vs Binance chain compared to quality of Contracts and RPCs

r/BitcoinSee Post

Security vulnerability in Bitcoin Knots (multiuser RPC only)

r/CryptoMoonShotsSee Post

ApeChain | L2 Blockchain specially designed for apes and monkeys | Zero GAS | Mainnet Live | Low Cap Gem | tons of potential. Check out our website and see for yourself.

r/CryptoCurrencySee Post

[Serious] How To Swap Moons on Arbitrum Nova

r/CryptoCurrencySee Post

I sent the wrong crypto to stake deposit. They said it’s unrecoverable. I just wanted to double check if it’s true.

r/CryptoCurrencySee Post

The Saga blockchain: The Multichain Gaming Hub of the Cosmos

r/CryptoMarketsSee Post

Secure your Blockchain node’s RPC interface with HAProxy

r/CryptoCurrencySee Post

Secure your node’s RPC interface with HAProxy

r/CryptoCurrencySee Post

A Simple Guide to Trading and Sending MOONs

r/CryptoCurrencySee Post

A Simple Guide to Trading and Sending MOONs

r/CryptoCurrencySee Post

How to navigate in MetaMask and sushiswap

r/CryptoCurrencySee Post

Selling and Swapping those precious MOON

r/BitcoinSee Post

Can I switch from using bitcoin-qt to bitcoin daemon without having to download the whole blockchain again

r/CryptoCurrencySee Post

PSA: you can import your Reddit vault on an already initialized Metamask using the private key

r/CryptoCurrencySee Post

A Simple Guide to Trading and Sending MOONs

r/BitcoinSee Post

Full Node - Mini PC recommendation

r/CryptoCurrencySee Post

Split MEV RPC Launch

r/CryptoCurrencySee Post

The Saga blockchain: The Interchain gaming Multiverse

r/CryptoMoonShotsSee Post

$NEAR Foundation Partners With Alibaba Cloud to Accelerate Web3 Growth in Asia

r/CryptoCurrencySee Post

Be wary of traditional finance taking over crypto. One day you might be swapping USDC for any token (SEC approved) on FEDswap through a regulated RPC (tracks everything). Be careful what you wish for.

r/BitcoinSee Post

unable to listen incoming transaction on using zeromq.

r/BitcoinSee Post

How to run a Full Node on OpenBSD

r/CryptoCurrencySee Post

Connecting Metamask to Sushiswap (Arbitrum Nova)

r/CryptoCurrencySee Post

Ankr's Enterprise RPC Services Goes Live on Microsoft’s Azure Marketplace

r/CryptoCurrencySee Post

Curio Cards artist Robek World launched a smart contracts coding game this week and the artwork is wild

r/CryptoCurrencySee Post

Curio Cards artist Robek World is launched a smart contracts coding game and the artwork is wild

r/CryptoCurrencySee Post

The Saga blockchain: The Interchain gaming Multiverse

r/CryptoMarketsSee Post

Pocket Network has never been closer to the launch of the v1. POKT V1 guarantees a reliable, performant, and cost effective RPC access to the open internet.

r/CryptoCurrencySee Post

Bitcoin Core version 25.0 has been Released!

r/BitcoinSee Post

Error when using +1 wallets in Bitcoin Core testnet (denpamusic/php-bitcoinrpc)

r/BitcoinSee Post

How do I connect latest ledger live to latest bitcoin core QT?

r/BitcoinSee Post

Can I get some help configuring BTC RPC Explorer to work with my node?

r/CryptoCurrencySee Post

Ankr releases Chiliz Chain 2.0 RPC

r/CryptoCurrencySee Post

Pulsechain bridge just launched $25mil+ queued for bridging in first day

r/CryptoCurrencySee Post

A SUPER-Beginner’s Guide to Swapping, Bridging and Exchanging MOONs

r/CryptoCurrencySee Post

MEV on L2's

r/CryptoCurrencySee Post

PulseChain is launching within 7 days. Here's how you get your tokens and bridge back value

r/CryptoCurrencySee Post

PulseChain is launching within 7 days. Here's how you can claim your free airdrop, and bridge value back

r/BitcoinSee Post

I get an Invalid Schnorr signature when trying to broadcast a taproot transaction

r/CryptoMoonShotsSee Post

Official OG Blockchain Blockchain Just launched its TESTNET flawlessly, road to mainnet just started stay tuned

r/CryptoCurrencySee Post

Reddit should choose communities with RCPs more carefully, it has been a failure in the fortnite sub

Mentions

Ethereum Layer 2 activity over the last week: | | | | | | | | | | :-: | :-: | :-: | :-: | :-: | :-: | :-: | :-: | | # | | Name | Past day TPS | 7d Change | Max daily TPS | 30D Count | Data source | | 1 | | Arbitrum Nova | 38.92 | -1.99% | 54.90on 2024 Mar 05 | 112 M | Blockchain RPC | | 2 | | Linea | 24.51 | +72.90% | 24.51on 2024 Mar 24 | 31.31 M | Blockchain RPC | | 3 | | Base | 16.68 | +30.18% | 23.98on 2024 Mar 16 | 23.02 M | Blockchain RPC | | 4 | | zkSync Era | 16.26 | +8.38% | 62.07on 2023 Dec 16 | 37.69 M | Blockchain RPC | | 5 | | Arbitrum One | 15.19 | +32.34% | 58.97on 2023 Dec 16 | 30.07 M | Blockchain RPC | | 6 | | Ethereum | 14.24 | +2.22% | 22.70on 2024 Jan 14 | 37.28 M | Blockchain RPC | | 7 | | OP Mainnet | 6.44 | +2.61% | 10.43on 2023 Jul 27 | 14.18 M | Blockchain RPC | | 8 | | Scroll | 5.39 | +4.11% | 6.29on 2024 Feb 25 | 9.27 M | Blockchain RPC | | 9 | | Blast | 4.20 | +56.41% | 9.40on 2024 Mar 01 | 7.91 M | Blockchain RPC | | 10 | | Immutable X | 2.76 | +23.91% | 39.35on 2022 Mar 11 | 6.53 M | Closed API | | 11 | | ApeX | 1.89 | -3.64% | 3.24on 2024 Feb 22 | 5.62 M | Closed API | | 12 | | Mode Network | 1.78 | +18.93% | 2.21on 2024 Feb 05 | 2.50 M | Blockchain RPC | | 13 | | Zora | 1.51 | +13.27% | 1.63on 2023 Aug 17 | 2.50 M | Blockchain RPC | | 14 | | Starknet | 1.36 | -50.78% | 12.30on 2024 Feb 20 | 5.63 M | Blockchain RPC | | 15 | | dYdX v3 | 0.82 | -52.29% | 11.45on 2022 Feb 15 | 5.43 M | Closed API | | 16 | | tanX | 0.69 | -5.56% | 1.22on 2024 Feb 18 | 2.12 M | Closed API | | 17 | | Manta Pacific | 0.54 | -20.81% | 5.88on 2023 Dec 22 | 1.39 M | Blockchain RPC | | 18 | | rhino.fi | 0.54 | +9.10% | 1.71on 2023 Nov 09 | 1.31 M | Closed API | | 19 | | Metis | 0.48 | +17.61% | 9.37on 2024 Jan 19 | 2.12 M | Blockchain RPC | | 20 | | Sorare | 0.38 | -8.32% | 2.31on 2022 Oct 23 | 1.47 M | Closed API | source: [https://l2beat.com/scaling/activity](https://l2beat.com/scaling/activity)

Mentions:#RPC#OP#API

Import seed phrase from vault into Metamask, add custom network Arbitrum Nova. RPC address is https://nova.arbitrum.io/rpc, block explorer url is https://nova-explorer.arbitrum.io/, currency symbol is ETH, and Chain ID is 42170. Then add the Moon wallet. Click import token, contract address is 0x0057Ac2d777797d31CD3f8f13bF5e927571D6Ad0, and token decimals is 18. Once added, you should see those MOONS!

Mentions:#RPC#ETH

Import seed phrase from vault into Metamask, add custom network Arbitrum Nova. RPC address is https://nova.arbitrum.io/rpc, block explorer url is https://nova-explorer.arbitrum.io/, currency symbol is ETH, and Chain ID is 42170. Then add the Moon wallet. Click import token, contract address is 0x0057Ac2d777797d31CD3f8f13bF5e927571D6Ad0, and token decimals is 18. Once added, you should see those MOONS!

Mentions:#RPC#ETH

Import seed phrase from vault into Metamask, add custom network Arbitrum Nova. RPC address is https://nova.arbitrum.io/rpc, block explorer url is https://nova-explorer.arbitrum.io/, currency symbol is ETH, and Chain ID is 42170. Then add the Moon wallet. Click import token, contract address is 0x0057Ac2d777797d31CD3f8f13bF5e927571D6Ad0, and taken decimals is 18. Once added, you should see those MOONS!

Mentions:#RPC#ETH

you can add the Arbitrum Nova network manually. Click Add Network > Custom Networks, then: Network Name - Arbitrum Nova New RPC URL - https://nova.arbitrum.io/rpc Chain ID - 42170 Currenty Symbol - ETH Block explorer URL - https://nova.arbiscan.io/

Mentions:#RPC#ETH

Ethereum Layer 2 activity over the last week, via [https://l2beat.com/scaling/activity](https://l2beat.com/scaling/activity) |#|Name|Past day TPS|7d Change|Max daily TPS|30D Count|Data source| |:-|:-|:-|:-|:-|:-|:-| |1||Arbitrum Nova|43.71|+12.06%|54.90 on 2024 Mar 05|93.51M|Blockchain RPC| |2||Base|15.39|+234.87%|21.29 on 2023 Sep 14|14.41M|Blockchain RPC| |3||Ethereum|15.19|+8.24%|22.70 on 2024 Jan 14|35.73M|Blockchain RPC| |4||Arbitrum One|15.09|+73.97%|58.97 on 2023 Dec 16|24.60M|Blockchain RPC| |5||zkSync Era|13.90|+20.27%|62.07 on 2023 Dec 16|38.71M|Blockchain RPC| |6||Linea|10.12|-2.80%|16.34 on 2024 Mar 09|22.79M|Blockchain RPC| |7||OP Mainnet|8.38|+99.93%|10.43 on 2023 Jul 27|12.06M|Blockchain RPC| |8||Starknet|3.90|+97.88%|12.30 on 2024 Feb 20|7.84M|Blockchain RPC| |9||Blast|3.35|+25.30%|9.40 on 2024 Mar 01|5.38M|Blockchain RPC| |10||dYdX v3|3.24|+67.63%|11.45 on 2022 Feb 15|5.15M|Closed API| |11||Scroll|2.84|+33.83%|6.29 on 2024 Feb 25|8.57M|Blockchain RPC| |12||Immutable X|2.82|+29.46%|39.35 on 2022 Mar 11|6.32M|Closed API| |13||ApeX|2.19|+13.36%|3.24 on 2024 Feb 22|6.33M|Closed API| |14||Mantle|2.08|-1.22%|25.47 on 2023 Dec 27|6.23M|Blockchain RPC| |15||Mode Network|1.19|+123.49%|2.21 on 2024 Feb 05|2.11M|Blockchain RPC| |16||Zora|1.13|+55.41%|1.63 on 2023 Aug 17|2.17M|Blockchain RPC| |17||Manta Pacific|0.78|+50.56%|5.88 on 2023 Dec 22|1.28M|Blockchain RPC| |18||Sorare|0.73|+2513.24%|2.31 on 2022 Oct 23|1.56M|Closed API| |19||DeGate V1|0.46|+55.78%|0.48 on 2024 Mar 05|565K|Explorer API| |20||[rhino.fi](http://rhino.fi)|0.45|+42.85%|1.71 on 2023 Nov 09|1.34M|Closed API|

Mentions:#RPC#OP#API

>You have to set up a totally new RPC endpoint in Metamask/whatever wallet so why not just make different scalable L1s that have nothing to do with Ethereum at that point? This is true because todays implementation is shit. But people can make wallets that bridge and switch networks without the user having to do anything. You can't just say these layers can reach the same security as ETH, the Trilemma remains an unsolved problem if you look at single layers. High scalability always results in lower security and/or decentralization. Building high scalable networks on top of a highly secure and decentralized one is the best solution we have found so far.

Mentions:#RPC#ETH

I don't really get the point of L2s either. They're supposed to help Ethereum scale, but at the same time it's like using an entirely different network anyway. You have to set up totally new RPC endpoint in metamask so why not just make different scalable L1s that have nothing to do with Ethereum? I just don't understand what the point is of complicating things by requiring Ethereum as a base layer. Can anyone explain?

Mentions:#RPC

Exactly. And all the support for each separate ecosystem for the devices is probably built by its own team. And that's just the UI. Then there are probably layers of backend systems the UIs talk to before the user input even finally reaches an RPC endpoint to execute a blockchain transaction.

Mentions:#RPC

By using the RPC API, any dev can easily track these whale wallets

Mentions:#RPC#API

Yubikey is just an MFA like an OTP or SMS message. These are generally for accounts tied to centralized entities. The web3 equivalent for that would be more like a multisig wallet, but the realistic thing for you to do is get a hardware wallet to use in conjunction with MetaMask or your hot wallet of choice. Furthermore, you should create different addresses on your hardware wallet for different purposes, eg. one address for DeFi, one address for HODLing, etc. Though geo-blocking for wallets can be at the RPC endpoint, in general it is merely happening on a DApp front end (the website giving a way to visually interact with the DApp) though not the DApp itself. Unfortunately, at least in the US, you're going to need to have a VPN handy for a lot of web3 content.

Mentions:#RPC

Been in and out since 2014 but didn't really start averaging in heavy until after 2021 but buying in 2014 and 2018/2019 even though small still made me money in 2020/2021. Lessons, the earlier you learn how to just look at tools to check trade volume, holding wallets, liquidity on DEXs, check what contract/ID a token corresponds too - you'll be much better prepared to interact with DeFi Just do 1 series of intro to AWS courses on Youtube. Now you'll be able to host pre-mainnet testnet nodes to farm airdrops. Any proof of work or these newer proof of spacetime coins, rent out compute, you can quickly farm coins/tokens the early months before they have any exchange listings Use multiple wallets. Like every mobile wallet it's easy to generate and manage numerous wallets. I have wallets for holding and wallets for interacting with contracts. Never been drained. I didn't use any hardware wallets. Use DeFi applications. Active users are the ones that get random airdrops. Split your funds. Like 80% doing nothing, 20% screw around. Actually learn how to use DeFi so you're not the guy that blames Uniswap/Pancakeswap/Raydium/the wallet that has a little interface in it for those/etc for why they bought the wrong coin, bought/sold with terrible slippage, the wallet RPC is down and claims their wallet stole their funds to people in the internet - just go on the blockchain explorer and check your address

Mentions:#RPC

A lot of people always use these moments of high traffic service overloads to promote going towards self custody and DEX tokens. That's good but I also assume people are using wallets where they access the blockchains through RPC nodes that can have the same issues, are not decentralized, and have users complain about the same service degradation

Mentions:#DEX#RPC

Oh please, I rewrote the whole Bitcoin client in VB dotnet and then C#. Initially my work was to use bitcoin-qt client in RPC mode and C# would be needed talk to the bitcoin-qt RPC but it just couldn't scale up because bitcoin-qt was never designed to handle many API requests, it would lock up or crash, so I had to port/write a fully working C# Bitcoin client from the reference bitcioin-qt client code. Yes, that also means having to write a wrapper for OpenSSL. Here's a bit I ported to VB dotnet

Mentions:#RPC#API

Nah, used Metamask for 3 years. As soon as I swapped to rabby, I only go back to metamask when there is brand new chains that rabby doesn't support right away. I also hate the Metamask now forces you to use the infura RPC for mainnet, which sells your IP information.

Mentions:#RPC

This is Helius the RPC provider, not Helium.

Mentions:#RPC

The bare minimum specs required to even send a request to read data. Try 1 index, 2 index and attempt to send a TX 🤣 Looking at 512gb RAM minimum and 24 cores. Also your cost and "gaming system" analogy is so wrong its beyond laughable. $10k minimum hardware if you want a node actually capable of performing work. In fact you can not only buy a gaming system but TV and surround sound system cheaper than 1 month of a quality RPC rental. Hahahahahahaha Barely 2k nodes on the network says it all. Thanks for the easy laughs today!

Mentions:#RAM#RPC

I think that’s wrong. POKT for example, would provide coordinated RPC communication both among (LLM) models, and to third party data sources like blockchains.

Mentions:#POKT#RPC

Not as simple as it sounds unfortunately. Fees on top of fees, bridging to a new blockchain, adding a custom RPC to metamask, etc... not to mention almost no exchange supports withdrawing directly to L2s. I was excited to try out Arbitrum until I realized how God damn frustrating the entire process is. It almost makes me wonder what is even the point of having L2s? To keep Ethereum alive and relevant?

Mentions:#RPC

An RPC that occurs on network. Not off network to a REST API. Stop being obtuse

Mentions:#RPC#API

An RPC that occurs on network. Not off network to a REST API

Mentions:#RPC#API

See my other response and continue there, it doesn't have to be a single node. They are spinning up a network of nodes, but we could do peer to peer relaying of contract states. I could set up a node now that uses RPC, TCP it doesn't matter.

Mentions:#RPC#TCP

> I don’t reme You used an RPC interface, client's do it on your behalf. It's a largely irrelevant step in the process.

Mentions:#RPC

yeah, these requirements are insane, it would cost almost $1000 to set up a system like this. the average user spends more on their gaming system. The specific system requirements will depend on the use of the node (and these can be tuned quite a bit for custom cases), but here are some rough starting guidelines: 12-core CPU with 2.8GHz clock speed minimum 128/256GB of RAM (RPC nodes might require more for custom database indices) 2-4 NVME drives of at least 1TB 10 Gbps Network Note that there are multiple validator software rewrites in process that aim to get more performance out of lesser hardware, Firedancer being the most prominent one

Mentions:#CPU#RAM#RPC

Until solana nodes are available to the average user like every other blockchain, it'll always just be a scam to make money selling data credits, rent servers, and rpc services. Selling RPC services makes more than staking by a long shot, funny how that's so intentionally designed while claiming "Moores law" nonsense while updating to multiple indexes and requiring more and more RAM. Again all designed intentionally to funnel people to their RPC service for rent. Hahahahaha.

Mentions:#RPC#RAM

Solana is just a centralized funnel to sell data credits and RPC services. That's where the real money is. If solana was so good of a blockchain as maxis claim they would have node requirements that meet the average home users hardware like every other network does. It's all smoke and mirrors to sell data and access.

Mentions:#RPC

> And no normies with their $1k of eth will ever do that, If Infura went down, then if they tried to use Ethereum through Metamask on the default RPC it wouldn't work. They would then go on Twitter or Reddit or Farcaster or wherever to find out why and would see the very simple instructions above. Literally 4 clicks and they would be back up and running. > or use anything other than metamask. They wouldn't need to... see above. > The fact of the matter is that eth is fiat with extra steps. That's literally nonsense. But you can say it's a 'fact' if it makes you feel comfortable. > We haven't even touched on staking centralization since eth went PoS, which inexplicably combined the validating segment of the network with its token segment, irreparably warping all kinds of incentives. I'm almost curious to know what nonsense you've been fed by the laser-eyed morons about how PoS works... but not enough to want to take this conversation down another rabbit hole and let you distract from your dumb claim about Infura.

Mentions:#RPC

It takes 4 clicks to change your RPC in Metamask. 1) Click the three dots to bring up the menu; 2) Click the word 'Settings'; 3) Click the word 'Networks'; 4) Click New RPC URL and change it to whatever you like. I usually use Frame and Safe as my wallets, but I still have Metamask and it has pointed to my node for years. Infura is the default, but it takes seconds to change. If there was ever a problem with Infura everyone would just switch to other options.

Mentions:#RPC

Pocket Network — The RPC Base Layer. Pocket Network is an open gateway that gives developers reliable and cost-effective RPC access to explore and build innovative solutions on any decentralized network. It has 99.9% uptime relays, over 17000 Nodes in 22 countries

Mentions:#RPC

Get in as soon as the liquidity is created and get out as fast as possible before it gets rugged. We don’t even check the price, buy a specified amount and sell at whatever market price. It’s still a work in progress but it’s been fun to learn about Solana and its speed. Got rugged a bunch, took small losses but also some decent wins (x2-x20) and so far one x500. Competition is brutal so don’t put your life savings on some random bot on a free RPC node or you’ll lose it all.

Mentions:#RPC
r/BitcoinSee Comment

I Saw a lot of mobile wallet using RPC providers, but if some really work like a self hosted node using SPV it's an awesome news for me. Even in the case of PCs, is there an advantage to download the full blockchain ? Why wouldn't that just be the role of miners?

Mentions:#RPC

It's probably going to happen more often after Firedancer is released. We've learned from Ethereum's multi-client design is that new clients have a higher chance of being instable and taking down the network if they exceed the liveness threshold of 33%. Though in the long run, Firedancer is a beefier client, so outages and Solana RPC instabilities should gradually reduce.

Mentions:#RPC

It's the opposite of absurdity. Blocking hackers and scammers is the only way to for crypto to move forward. It's way too insecure for anyone right now, even if you have the best private key management and do not connect any sites to your wallet you can still be a victim if the protocol you invest in gets drained. It happens every day. Censoring the hackers and scammers is a good thing, even if there will be loopholes and workarounds. Its Worthwhile making their activities as hard as possible. I agree such penalties should be decided by the community, but wait Uniswap is a DAO so they do have public governance. so I wonder why hasnt Mr zoltu created a governance proposal for replacing the infura RPC with his personal one ? Probably because he knows the community would have rejected such bullshit.

Mentions:#DAO#RPC

This dude wanted to change Uniswaps Infura RPC (infura = the biggest RPC provider in the world) to his own shitty RPC (probably some nasty pc in his dorm room) and complains why Uniswap did not accept this change.

Mentions:#RPC

The trouble is people don’t know how to use it. MM is an OG wallet that connects to most things. Anyone can see your wallet activity.. believe it. It’s pretty simple to run up a node and use your own RPC. If mm airdrop people will still be upset as they didn’t use it… catch 22. I predict MM will make a massive upgrade this year. Taylor will provide the goods as she always does.

Mentions:#MM#RPC

MM is fine. I use it for obscure chains and testnets that aren't supported on other wallets. But they are leagues behind most of their competitors nowadays. They also share your wallet activity and their RPC suppliers, infura, has been known to share your IP address.

Mentions:#MM#RPC

If you're having trouble claiming your JUP airdrop, it's probably because Triton the default Jupiter RPC sucks. Try switching to Helius under settings.

Mentions:#JUP#RPC

ETH of the 50%+ OFAC compliance? ETH of the 72 million ETH premine? ETH of ConsenSys and Infura RPC? ETH of MEV milking uneducated and unsuspecting retail users? This is what classic WallStreet drools over, a cash machine milking the masses. If you goal was more power to the plutocracy you certainly accomplished it. Congrats on this, seriously.

Mentions:#ETH#RPC#MEV
r/BitcoinSee Comment

Driving the Bitcoin RPC is pretty simple [https://developer.bitcoin.org/reference/rpc/index.html](https://developer.bitcoin.org/reference/rpc/index.html) you can easily get the block hash for each height and the TX for each block etc. There are example projects (two random ones from a google search here: [https://github.com/in3rsha/bitcoin-utxo-dump](https://github.com/in3rsha/bitcoin-utxo-dump) (golang) + [https://github.com/Mrwh0/bitcoin-utxo-dump](https://github.com/Mrwh0/bitcoin-utxo-dump) (python) which you could modify to your purpose)

Mentions:#RPC

**About Riddle #9** This last riddle is insanely hard because there are so many steps, requires some basic dev knowledge (if you don't want to manually brute force 200 seeds). And the very last step is stupid since it's so easy to miss. Pretty much impossible to solve on your own in reasonable time, but maybe possible to solve on your own with these hints. It's about 10x longer than Riddle #8. There's a basehunt channel on the Base Discord server where where you can get an invite to the group that solved it. There are enough breadcrumbs on that special Discord server to help you solve it. Alternatively, here are barely enough hints to solve it on your own, but it will definitely require a lot of persistence. Basically, this contains most of the relevant breadcrumbs. -------------- **Breaking down each of the riddle's lines** > Event hides, in attendance it resides. This is referring to a special, well-known type of NFT if you've been deep in the Etheruem ecosystem. >!These NFTs have event numbers, and that's where the title comes in. This NFT's page will provide info to get to a special secret website.!< If you have trouble scanning a particular code on that page, try using another phone. It does work, it's just very blurry, and I had to try multiple times. > In binary's tongue, find numbers yet unsung. You actually need to use this trick twice: >!once to unlock the website, and once each later on to access 2 of the 3 riddle pages on the website after you find the website. Remember, binary numbers can be converted to more than just decimals.!< >!That's not one long binary number. That's 7 separate binary numbers!< Once you find the website, enter the password to get in. This is one of those riddle websites where you can just type a code after the website's address in the address bar to get to a page. (e.g. website.xxx/code). >!The 3 codes are numbers. The first page you land on will provide 2 of the 3 codes.!< > Date of birth, not human, yet still of worth. Use to hint to access the 3rd riddle page of the website. This "birth" is in yyyymmddhhmmss format. >!This "birth" is related to the riddle website you just entered, and you can find this date on one of many public 3rd-party websites.!< > Twelve in a row, find them so I can show. Should be pretty obvious what you're trying to find. Now finding it is much harder. Each of the 3 pages will give you exactly 4 of the 12. You need to have basic Solidity dev knowldge to brute force this, but if you aren't, I will help you narrow down the choices so that you can test manually. (It'll still take a couple of minutes to test all choices manually. Metamask will warn you if the seed does not pass the checksum, so you can just refresh Metamask and try again.) This is the order of pages by their titles: 1. >!About 2 (already in order)!< 1. >!General 3 (1 word from each line, lines are already in order)!< 1. >!About 3 (already in order)!< If you want to brute force the seed the way we first solved it, here's one method: const wallet = ethers.HDNodeWallet.fromPhrase(seed) console.log(seed + " - " + await wallet.getAddress()); And then I used a Quicknode RPC provider and "provider.getTransactionCount(address, 'latest')" to check if the account had any transactions. > Say the secret words, from wallet's depths it's heard. To save you time, I'll let you know that you only need to check under the primary account of the seed. (I used a script to check 60+ additional accounts under the same seed and found no activity in them (using both BIP-32 and BIP-43 methods for address generation). >!There are some strange transactions from the wallet's account.!< >!Within one of the transactions, after decoding, on one line among many, you'll find the final location and where to go next.!< You're now at the final hunt. The next part threw me off. I wasted so much time searching on the official location/website for a phrase. It's not there, at least not in any obvious location. The final words you need to message the bot are actually on a specific part of a Google page about the final location. (It's also on some 3rd party websites about the final location, but you'd have to dig super hard.) It's not an obvious phrase. > Hint: Goodluck... Yep. You'll definitely need either need insane luck or a group to solve this. The word "goodluck" is not relevant to solving the puzzle.

Mentions:#RPC#BIP
r/CryptoCurrencySee Comment

Sounds like your RPC is not connected, which wierd but easy to fix, just pick a different one from chainlist. https://chainlist.org/chain/1

Mentions:#RPC
r/CryptoCurrencySee Comment

Snaps were introduced to Metamask about 4 months ago. There are [dozens already](https://snaps.metamask.io/explore/) and the fact that one more has been added is not a 'Metamask advancement' any more than adding another chain's RPC to the wallet.

Mentions:#RPC
r/CryptoCurrencySee Comment

> other chains have a lot more room to grow without the technical headache of actually scaling properly. I think this obviously comes down to the definition of 'properly'. In my opinion two of the most fundamentally important aspects of cryptocurrencies are: * Permissionlessness - any users can interact directly with whoever and whatever they like, and; * Trustlessness - users do not need to rely on the entities they interact with to be honest. The only way to achieve this is for users to be able to run nodes if they wish. Full nodes give you the ability to connect to the network yourself, check balances without relying on 3rd party explorers, post transactions without relying on 3rd party RPC providers etc. For most of the chains that claim to have solved scaling, they do this by making transactions faster in one way or another. This means the clients that run the network have higher hardware and connection requirements, which makes running a full node unrealistic for regular users. As an example, to run a node that would let you check your balance or post a transaction on Solana requires at minimum a 1GB/s internet connection and 256 GB of RAM. For comparison, the PC I use for playing DCS in VR has 64 GB. On the other hand, I'm running an Ethereum node and an Optimism L2 node on $200 Rock 5b single board computers (~ $450 when you factor in SSDs, cases, fans, power supplies etc). So yea, some chains have scaled to offer much cheaper transactions, but the tradeoff that their marketing never mentions is that no normal users will ever be able to actually post a transaction themseves or verify any balanced... which in my opinion means you may as well just use the traditional banking system!

r/CryptoCurrencySee Comment

Amazing entry on Neon for anybody who likes the parallelized EVM plays Total capitulation on RPC fud

Mentions:#RPC
r/CryptoCurrencySee Comment

tldr; Radix has partnered with Grove to enhance the developer experience (DevEx) in decentralized finance (DeFi). Radix is a Layer 1 smart contract platform that aims to improve the user and developer experience in Web3 and DeFi with innovations like a human-readable transaction model and a new programming language called Scrypto. The Radix Babylon Mainnet Upgrade launched in September 2023, and several projects are now live with more to come. The partnership with Grove expands access to Radix's ecosystem, allowing developers to build dApps with Scrypto and Radix Engine, supported by Grove's reliable and efficient RPC nodes. *This summary is auto generated by a bot and not meant to replace reading the original article. As always, DYOR.

Mentions:#RPC#DYOR
r/CryptoCurrencySee Comment

The integration empowers developers by offering top-tier, dependable, decentralized access to Radix RPC nodes. Through its widespread global reach, Grove significantly amplifies access to the Radix ecosystem.

Mentions:#RPC
r/CryptoCurrencySee Comment

Pocket Network (POKT) A real OG of DePIN niche, project that created DePIN back in 2016 and project that is creating once again a new niche DePIN + AI = DecAI. 1. POKT is decentralized RPC, which is basically decentralized Infura. It provides decentralized RPC access to Uniswap, it will soon be able to serve LLMs and AI requests, and more. 2. DePIN where users use their own hardware to run POKT nodes that can serve any requests in a decentralized, affordable and scalable way. High performance RPC with lower latency than centralized Infura. 3. POKT partnered with Infura, largest centralized RPC provider in the world. 4. The more POKT protocol is being used, the more POKT coins it is burning. Gateway operators that are serving requests have to burn small part of POKT for each served request. It is currently around $30k per month burn. It can tracked transparently on poktscan website. 5. No exact number, but there are 700+ wPOKT holders and probably thousands of users because network serves around 500 million relays daily. 6. 300 million USD market cap. 7. POKT price is $0.20 right now. 8. Circulating supply 1.6B. All coins are in circulation. Some other important info: backed by Fidelity-affiliated Avon Ventures, successfully raised $7.9M to fund development. POKT uses its own blockchain, but it is also available as wPOKT on Uniswap, wPOKT is wrapped version of POKT on ERC-20 chain. DYOR.

r/CryptoCurrencySee Comment

Still, $500/mo isn't bad for the amount of data being digested. It's the same cost as running a Polygon PoS node. Not sure how much it is for Arbitrum and Optimism, but I can't imagine it being much cheaper than that based on the amount of data they produce. Bitcoin is the cheapest ($25/mo) by far because it last the least amount of data and traffic. Ethereum is about $50-200/mo depending on what type of data you're indexing. $500/mo is 10x cheaper than running a Solana RPC and 100x cheaper than a Solana Archive RPC, which is $500k a year. Almost all fast networks are going to end up being very expensive because cost scales linearly with data transfer and storage.

Mentions:#RPC

POKT is unbelieveably amazing web3 infra RPC provider. Lowest latency through Nodies gateway to POKT protocol, and it is decentralized at the same time. I've never seen so far someone solving RPC trillemma successfully. Booolish!

Mentions:#POKT#RPC

POKT is still in its embrionic phase, although it already stands out. It did 10x past 3 months, but its market cap is still under $300M. Confirmed partnership with largest RPC provider (Infura), solid VC backing ($8M) by Fidelity-affiliated VC, more partnerships on horizon and still not listed on any major Tier 1 exchange (except Kucoin). Biggest potential lies in (not yet unlocked) capability to offer decentralized computing for all LLMs and any other open source apps that require high-performance decentralized computing. Research this one on Twitter, a lot of buzz around it. It might enter a big league soon with giants like Solana and Chainlink.

Mentions:#POKT#RPC#VC
r/CryptoCurrencySee Comment

Wow, "hat speech"....anyway: September 14, 2021: Down for 17 hours 12 minutes due to a DDoS attack on a decentralised exchange(DEX). January 6 – 8, 2022: Outage for multiple days. Presumably DDoS attack. January 10, 2022: Assumed to be the same DDoS attack. January 22, 2022: 29 hours of downtime, lots of duplicate transactions causing congestion and outages. March 28, 2022: RPC nodes forked off when upgrade to v1.9 happened. April 30, 2022: seven hour outage due to millions of NFTs being minted. May 27, 2022: Block times delayed up to 30 minutes. June 1, 2022: “A runtime bug triggered by the durable nonce transactions feature allowed, under a specific set of circumstances, for a failed durable nonce transaction to be processed twice.” Lasted about 5 hours. October 1, 2022: A misconfigured node resulted in lost data and needs to restart from a previous point, which apparently crashes the entire chain. February 28, 2023: “Solana Mainnet is experiencing a large forking event right now, validators are investigating to determine the network health, root cause and next steps. Transactions may fail right now”. Lasted for about 20 hours.

Mentions:#DEX#RPC
r/CryptoCurrencySee Comment

Pokt network Partnered with Infura to deliver decentralized RPC. Received $8 mln funding from Fidelity affiliate and more. Team survived bear market and lowered inflation to around 5%. Actual revenue bringing business model. Branching out to LLM/AI. Low market cap. Huge upside potential. Upcoming announcement of partnership with XRP (rumored). Upcoming tier 1 cex in Q2 2024. Where to get: POKT on MEXC/Kucoin/Gate or dex (wrapped POKT).

Mentions:#RPC#XRP#POKT
r/CryptoCurrencySee Comment

Ah. Permissioned right now alas. They call it an “external node” (RPC node really), but it only works with an initial SQL snapshot, and it’s not permissionless. Yet, I hope. Our repo for it is here, but without the SQL snapshot it won’t do much: https://github.com/CryptoManufaktur-io/era-docker

Mentions:#RPC
r/CryptoCurrencySee Comment

1) can happen, it’s inherent to the design of Solana. Has to do with how they do finality and liveness. I’ve described that before so won’t again here 2) sounds like FUD even to me, and I’m an Ethereum maxi (as in I run two Solana RPC nodes, but most of my nodes are EVM chains). Don’t pay attention to price action. Focus only on tech. Run nodes. It won’t get you rich, but it’s more fun.

Mentions:#FUD#RPC
r/CryptoCurrencySee Comment

Holding POKT Network for a while now They recently partnered with Infura to deliver decentralized RPC services. Also they are branching into LLM/AI And they recently received $8 mln funding from Fidelity affiliate. They survived bear market. Lowered inflation dramatically. Rumors of new partnership with XRP, will be public within 1 month or earlier. Tier 1 cex in q2 2024 Use case to secure the network just like Link The coin is available on KuCoin, Gate and wrapper version wpokt on Uniswap.

Mentions:#POKT#RPC#XRP
r/CryptoCurrencySee Comment

*Your voting power could not be calculated. This is often due to a misconfigured strategy or an unresponsive RPC node involved in the strategy* I have been connected to Snapshot before, as with EthTrader, but tyhey have also had some recent issues with users being unable to vote

Mentions:#RPC
r/CryptoCurrencySee Comment

I've joined the space prior to voting and I'm still getting the same error message: "Your voting power could not be calculated. This is often due to a misconfigured strategy or an unresponsive RPC node involved in the strategy. If the problem persists, consider contacting the space admin or our support team on"

Mentions:#RPC
r/CryptoCurrencySee Comment

I keep getting this error: "Your voting power could not be calculated. This is often due to a misconfigured strategy or an unresponsive RPC node involved in the strategy. If the problem persists, consider contacting the space admin or our support team on" Any idea why?

Mentions:#RPC
r/CryptoCurrencySee Comment

I'm getting an error message after connecting wallet (Metamask): 'our voting power could not be calculated. This is often due to a misconfigured strategy or an unresponsive RPC node involved in the strategy.' Did I mess something up? Is there a fix?

Mentions:#RPC
r/BitcoinSee Comment

I used Electrs a few years ago with my own bitcoin node. As far as I remember, Electrs accesses the data files emitted by bitcoind and uses this to build its own database. Maybe things have changed since then and you don't need your own node, but it's still best to run your own node. If it's using the RPC interface the RPC username and password are only needed if the node is exposed on the internet.

Mentions:#RPC
r/CryptoCurrencySee Comment

Has anyone heard about rumors that POKT is partnering with Ripple for the upcoming Ripple Payments? This seems like a big deal for a smaller RPC provider like $POKT with a $150m market cap. If POKT gets involved in handling requests for cross-chain transfers used by Ripple Payments, it could significantly boost demand for the POKT protocol. Decentralizing the RPC layer makes sense for Ripple, but this partnership almost sounds too good to be true. Any thoughts or insights on this?

Mentions:#POKT#RPC
r/CryptoCurrencySee Comment

POKT seems like a cool project and the developers are definitely thinking long term. The current issue I have is that defi developers who want to access their RPC nodes do not have to spend POKT in order to do so, they just have to stake POKT. Rewards for running a RPC node come from newly minted POKT (re. inflation) and the value captured by node providers needs to come from somewhere. Is it the node providers themselves whose rewards are less then the inflation rate? The developers accessing the nodes whose staked POKT loses value to inflation? Or retail traders who buy and hold the coin but don't do anything with it believing it will gain value due to hype? That being said, The POKT team plans to shift away from the inflation model at some point in the future so I believe this project is headed in the right direction and I am excited for what they might do!

Mentions:#POKT#RPC
r/CryptoCurrencySee Comment

Ethereum L2 activity update for the past week, via https://l2beat.com/scaling/activity: | | | | | | | | |:-:|:-:|:-:|:-:|:-:|:-:|:-:| | # | Name | Past day TPS | 7d Change | Max daily TPS | 30D Count | Data source | | 1 | Ethereum | 13.42 | +3.56% | 22.37on 2022 Dec 09 | 33.11 M | Blockchain RPC | | 2 | zkSync Era | 10.38 | +49.90% | 15.25on 2023 Aug 26 | 20.30 M | Blockchain RPC | | 3 | Arbitrum One | 8.18 | +29.97% | 31.64on 2023 Mar 23 | 22.67 M | Blockchain RPC | | 4 | Linea | 6.30 | +70.15% | 9.93on 2023 Dec 03 | 11.25 M | Blockchain RPC | | 5 | dYdX v3 | 3.65 | +43.78% | 11.45on 2022 Feb 15 | 12.23 M | Closed API | | 6 | OP Mainnet | 3.53 | +13.48% | 10.43on 2023 Jul 27 | 9.10 M | Blockchain RPC | | 7 | Mantle | 2.99 | +38.10% | 4.41on 2023 Oct 15 | 5.51 M | Blockchain RPC | | 8 | Arbitrum Nova | 2.86 | +50.19% | 10.93on 2023 Apr 27 | 4.81 M | Blockchain RPC | | 9 | Base | 2.55 | -0.02% | 21.29on 2023 Sep 14 | 7.15 M | Blockchain RPC | | 10 | Starknet | 2.43 | -57.42% | 10.21on 2023 Nov 25 | 11.98 M | Blockchain RPC | | 11 | Immutable X | 2.19 | -46.01% | 39.35on 2022 Mar 11 | 7.07 M | Closed API | | 12 | ApeX | 1.66 | +8.06% | 2.09on 2023 Dec 06 | 4.53 M | Closed API | | 13 | Scroll | 1.03 | +40.43% | 5.03on 2023 Nov 09 | 3.09 M | Blockchain RPC | | 14 | Manta Pacific | 0.89 | +49.91% | 2.38on 2023 Nov 26 | 1.80 M | Blockchain RPC | | 15 | zkSync Lite | 0.44 | -12.57% | 3.29on 2023 Mar 21 | 935 K | Explorer API | | 16 | Sorare | 0.38 | -21.41% | 2.31on 2022 Oct 23 | 1.31 M | Closed API | | 17 | Zora | 0.37 | -24.19% | 1.63on 2023 Aug 17 | 1.07 M | Blockchain RPC | | 18 | rhino.fi | 0.29 | +66.32% | 1.71on 2023 Nov 09 | 1.19 M | Closed API | | 19 | Polygon zkEVM | 0.20 | -63.15% | 1.41on 2023 Aug 04 | 1.27 M | Blockchain RPC | | 20 | Brine | 0.16 | -0.58% | 0.92on 2023 Nov 20 | 812 K | |

Mentions:#RPC#API#OP
r/BitcoinSee Comment

A new RPC getaddrmaninfo has been added to view the distribution of addresses in the new and tried table of the node’s address manager across different networks(ipv4, ipv6, onion, i2p, cjdns). The RPC returns count of addresses in new and tried table as well as their sum for all networks. (#27511) A new importmempool RPC has been added. It loads a valid mempool.dat file and attempts to add its contents to the mempool. This can be useful to import mempool data from another node without having to modify the datadir contents and without having to restart the node. (#27460) Warning: Importing untrusted files is dangerous, especially if metadata from the file is taken over. If you want to apply fee deltas, it is recommended to use the getprioritisedtransactions and prioritisetransaction RPCs instead of the apply_fee_delta_priority option to avoid double-prioritising any already-prioritised transactions in the mempool. Updated settings bitcoind and bitcoin-qt will now raise an error on startup if a datadir that is being used contains a bitcoin.conf file that will be ignored, which can happen when a datadir= line is used in a bitcoin.conf file. The error message is just a diagnostic intended to prevent accidental misconfiguration, and it can be disabled to restore the previous behavior of using the datadir while ignoring the bitcoin.conf contained in it. (#27302) Passing an invalid -debug, -debugexclude, or -loglevel logging configuration option now raises an error, rather than logging an easily missed warning. (#27632) Changes to GUI or wallet related settings can be found in the GUI or Wallet section below. New settings Tools and Utilities A new bitcoinconsensus_verify_script_with_spent_outputs function is available in libconsensus which optionally accepts the spent outputs of the transaction being verified. A new bitcoinconsensus_SCRIPT_FLAGS_VERIFY_TAPROOT flag is available in libconsensus that will verify scripts with the Taproot spending rules. Wallet Wallet loading has changed in this release. Wallets with some corrupted records that could be previously loaded (with warnings) may no longer load. For example, wallets with corrupted address book entries may no longer load. If this happens, it is recommended load the wallet in a previous version of Bitcoin Core and import the data into a new wallet. Please also report an issue to help improve the software and make wallet loading more robust in these cases. (#24914) The gettransaction, listtransactions, listsinceblock RPCs now return the abandoned field for all transactions. Previously, the “abandoned” field was only returned for sent transactions. (#25158) The listdescriptors, decodepsbt and similar RPC methods now show h rather than apostrophe (') to indicate hardened derivation. This does not apply when using the private parameter, which matches the marker used when descriptor was generated or imported. Newly created wallets use h. This change makes it easier to handle descriptor strings manually. E.g. the importdescriptors RPC call is easiest to use h as the marker: '["desc": ".../0h/..."]'. With this change listdescriptors will use h, so you can copy-paste the result, without having to add escape characters or switch ' to ‘h’ manually. Note that this changes the descriptor checksum. For legacy wallets the hdkeypath field in getaddressinfo is unchanged, nor is the serialization format of wallet dumps. (#26076) The getbalances RPC now returns a lastprocessedblock JSON object which contains the wallet’s last processed block hash and height at the time the balances were calculated. This result shouldn’t be cached because importing new keys could invalidate it. (#26094) The gettransaction RPC now returns a lastprocessedblock JSON object which contains the wallet’s last processed block hash and height at the time the transaction information was generated. (#26094) The getwalletinfo RPC now returns a lastprocessedblock JSON object which contains the wallet’s last processed block hash and height at the time the wallet information was generated. (#26094) Coin selection and transaction building now accounts for unconfirmed low-feerate ancestor transactions. When it is necessary to spend unconfirmed outputs, the wallet will add fees to ensure that the new transaction with its ancestors will achieve a mining score equal to the feerate requested by the user. (#26152) For RPC methods which accept options parameters ((importmulti, listunspent, fundrawtransaction, bumpfee, send, sendall, walletcreatefundedpsbt, simulaterawtransaction), it is now possible to pass the options as named parameters without the need for a nested object. (#26485) This means it is possible make calls like: src/bitcoin-cli -named bumpfee txid fee_rate=100 instead of src/bitcoin-cli -named bumpfee txid options='{"fee_rate": 100}' The deprecatedrpc=walletwarningfield configuration option has been removed. The createwallet, loadwallet, restorewallet and unloadwallet RPCs no longer return the “warning” string field. The same information is provided through the “warnings” field added in v25.0, which returns a JSON array of strings. The “warning” string field was deprecated also in v25.0. (#27757) The signrawtransactionwithkey, signrawtransactionwithwallet, walletprocesspsbt and descriptorprocesspsbt calls now return the more specific RPC_INVALID_PARAMETER error instead of RPC_MISC_ERROR if their sighashtype argument is malformed. (#28113) RPC walletprocesspsbt, and descriptorprocesspsbt return object now includes field hex (if the transaction is complete) containing the serialized transaction suitable for RPC sendrawtransaction. (#28414) It’s now possible to use Miniscript inside Taproot leaves for descriptor wallets. (#27255) GUI changes The transaction list in the GUI no longer provides a special category for “payment to yourself”. Now transactions that have both inputs and outputs that affect the wallet are displayed on separate lines for spending and receiving. (gui#119) A new menu option allows migrating a legacy wallet based on keys and implied output script types stored in BerkeleyDB (BDB) to a modern wallet that uses descriptors stored in SQLite. (gui#738) The PSBT operations dialog marks outputs paying your own wallet with “own address”. (gui#740) The ability to create legacy wallets is being removed. (gui#764) Low-level changes Tests Non-standard transactions are now disabled by default on testnet for relay and mempool acceptance. The previous behaviour can be re-enabled by setting -acceptnonstdtxn=1. (#28354)

Mentions:#RPC
r/BitcoinSee Comment

Bitcoin Core installation binaries can be downloaded from bitcoincore.org and the source-code is available from the [Bitcoin Core source repository](https://github.com/bitcoin/bitcoin). 26.0 Release Notes Bitcoin Core version 26.0 is now available from: https://bitcoincore.org/bin/bitcoin-core-26.0/ This release includes new features, various bug fixes and performance improvements, as well as updated translations. Please report bugs using the issue tracker at GitHub: https://github.com/bitcoin/bitcoin/issues To receive security and update notifications, please subscribe to: https://bitcoincore.org/en/list/announcements/join/ How to Upgrade If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes in some cases), then run the installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on macOS) or bitcoind/bitcoin-qt (on Linux). Upgrading directly from a version of Bitcoin Core that has reached its EOL is possible, but it might take some time if the data directory needs to be migrated. Old wallet versions of Bitcoin Core are generally supported. Compatibility Bitcoin Core is supported and extensively tested on operating systems using the Linux kernel, macOS 11.0+, and Windows 7 and newer. Bitcoin Core should also work on most other Unix-like systems but is not as frequently tested on them. It is not recommended to use Bitcoin Core on unsupported systems. Notable changes P2P and network changes Experimental support for the v2 transport protocol defined in BIP324 was added. It is off by default, but when enabled using -v2transport it will be negotiated on a per-connection basis with other peers that support it too. The existing v1 transport protocol remains fully supported. Nodes with multiple reachable networks will actively try to have at least one outbound connection to each network. This improves individual resistance to eclipse attacks and network level resistance to partition attacks. Users no longer need to perform active measures to ensure being connected to multiple enabled networks. (#27213) Pruning When using assumeutxo with -prune, the prune budget may be exceeded if it is set lower than 1100MB (i.e. MIN_DISK_SPACE_FOR_BLOCK_FILES * 2). Prune budget is normally split evenly across each chainstate, unless the resulting prune budget per chainstate is beneath MIN_DISK_SPACE_FOR_BLOCK_FILES in which case that value will be used. (#27596) Updated RPCs Setting -rpcserialversion=0 is deprecated and will be removed in a future release. It can currently still be used by also adding the -deprecatedrpc=serialversion option. (#28448) The hash_serialized_2 value has been removed from gettxoutsetinfo since the value it calculated contained a bug and did not take all data into account. It is superseded by hash_serialized_3 which provides the same functionality but serves the correctly calculated hash. (#28685) New fields transport_protocol_type and session_id were added to the getpeerinfo RPC to indicate whether the v2 transport protocol is in use, and if so, what the session id is. A new argument v2transport was added to the addnode RPC to indicate whether a v2 transaction connection is to be attempted with the peer. Miniscript expressions can now be used in Taproot descriptors for all RPCs working with descriptors. (#27255) finalizepsbt is now able to finalize a PSBT with inputs spending Miniscript-compatible Taproot leaves. (#27255) Changes to wallet related RPCs can be found in the Wallet section below. New RPCs loadtxoutset has been added, which allows loading a UTXO snapshot of the format generated by dumptxoutset. Once this snapshot is loaded, its contents will be deserialized into a second chainstate data structure, which is then used to sync to the network’s tip. Meanwhile, the original chainstate will complete the initial block download process in the background, eventually validating up to the block that the snapshot is based upon. The result is a usable bitcoind instance that is current with the network tip in a matter of minutes rather than hours. UTXO snapshot are typically obtained via third-party sources (HTTP, torrent, etc.) which is reasonable since their contents are always checked by hash. You can find more information on this process in the assumeutxo design document (https://github.com/bitcoin/bitcoin/blob/master/doc/design/assumeutxo.md). getchainstates has been added to aid in monitoring the assumeutxo sync process. A new getprioritisedtransactions RPC has been added. It returns a map of all fee deltas created by the user with prioritisetransaction, indexed by txid. The map also indicates whether each transaction is present in the mempool. (#27501) A new RPC, submitpackage, has been added. It can be used to submit a list of raw hex transactions to the mempool to be evaluated as a package using consensus and mempool policy rules. These policies include package CPFP, allowing a child with high fees to bump a parent below the mempool minimum feerate (but not minimum relay feerate). (#27609) Warning: successful submission does not mean the transactions will propagate throughout the network, as package relay is not supported. Not all features are available. The package is limited to a child with all of its unconfirmed parents, and no parent may spend the output of another parent. Also, package RBF is not supported. Refer to doc/policy/packages.md for more details on package policies and limitations. This RPC is experimental. Its interface may change.

r/CryptoCurrencySee Comment

For those who have purchased TAO… where are you storing it? MetaMask won’t accept the RPC URL. https://rpc.testnet.tao.network 🧐 not sure how to get it off the MEXC exchange.

Mentions:#TAO#RPC
r/CryptoCurrencySee Comment

POKT is my top pick. POKT has raised $7.9M from Fidelity-affiliated Avon Ventures, Placeholder Capital (ARK Invest) and Druid Ventures. POKT is in DePIN niche capable of serving relays for all open-source projects, including LLMs, which has extremely big potential to skyrocket the price. Also, POKT partnered with Infura, leading centralized RPC provider as its main decentralized RPC provider. DYOR.

r/BitcoinSee Comment

Bitcoin core is weird because it technically is the node AND wallet, so I use Bitcoin core, but not the wallet features. I can enter all those RPC commands on the server I run Bitcoin core on, though obviously the wallet-related ones aren't much use in that context. Sparrow also handled PBST (: it's a really dope wallet imo

Mentions:#RPC
r/BitcoinSee Comment

If you are running Bitcoin Core, you can see the total amount in circulation using the RPC call gettxoutsetinfo (in the Bitcoin-Qt debug console, or using bitcoin-cli if you run bitcoind).

Mentions:#RPC
r/CryptoCurrencySee Comment

After reading all of your responses you are absolutely going to lose your money if you don’t STOP and learn the basics about how crypto works. You have a whole bunch of fundamental misunderstandings. A better word for “wallet” is “keychain.” It does not store your funds. It stores the *access* to your funds (your private key). Funds are on the blockchain, not the wallet. The wallet looks at the chain. Gas fees are a function of the chain, not the wallet. BTC has to be sent on the BTC chain and the fees to do so are a function of how busy the chain is. You pay ETH gas to move any erc20 token on ETH. You pay AVAX gas to move funds on Avalanche. You pay MATIC gas to move funds on Polygon. MetaMask can interact with many chains. By default it only has the ETH layer 1. But you can add BNB, Polygon, Arbitrum, Avalanche, etc. Adding the RPC to your MetaMask allows you to use those chains. It does facilitate sending ETH on the BRC network. To move a token from its native chain to another, it must be bridged. A bridge locks up assets on one chain and gives you a wrapped version on the new chain (eg BTC on the bitcoin network to WBTC on Ethereum). Tokens MUST be sent on their native chain. If you try to send ETH to a BTC address without bridging, it’s gone forever. Did you catch that part? This is why you are at high risk of losing your funds right now. Based on your responses, you are trying very hard to do something that will burn those tokens for good. Stop. Learn about the differences between wallets, chains, and tokens. Don’t try to send anything until you learn exactly what you want to do and how that is done. If you experiment the way you are going, you’re going to burn your assets.

Pocket Network is entering AI RPC niche which is huge, but completely untapped area. There is no competition in AI RPC, being pioneer in this niche will print new millionaires. Mark my word.

Mentions:#RPC
r/CryptoMarketsSee Comment

Well, looks like Infura and Pocket Network are teaming up to create unstoppable and permissionless RPC access to Web3 blockchain infrastructure. Who needs centralized providers when you have a dynamic duo like that? Guess they took the phrase decentralize everything a little too seriously. Don't you just love it when crypto companies try to outdo each other in the most regarded way possible? [Buy RIOT](https://marketchameleon.com/Overview/RIOT/?lu=true&pap_aid=stormofnegativity&pap_cid=11111111) and watch the chaos unfold.

Mentions:#RPC#RIOT
r/BitcoinSee Comment

And this advice is useless and misguided. If you just run bitcoin core - it is useless for everyone. For you - because you can't connect to it for anything useful without an electrum server. Ok, you can do RPC commands on it. But if you know how to do it, you wouldn't ask such questions in the first place. For anyone else or network security it is useless because your ports are closed and nobody sees your node.

Mentions:#RPC
r/CryptoMarketsSee Comment

Andrew has 200k twitter followers. Well known expert. POKT is decentralized RPC provider. Infura is largest centralized RPC provider. POKT partnered with Infura to provide them decentralized node infrastructure service. This was quite a big deal with Microsoft involved. POKT is main decentralized node infra provider in the deal. Check it out: [https://cointelegraph.com/press-releases/infura-partners-with-microsoft-tencent-and-16-others-to-build-decentralized-infrastructure-network](https://cointelegraph.com/press-releases/infura-partners-with-microsoft-tencent-and-16-others-to-build-decentralized-infrastructure-network)

Mentions:#POKT#RPC
r/CryptoMarketsSee Comment

POKT guys. Huge potential in the decentralized node infrastructure space. Probably the most important DePIN and RPC project that retail isn't aware of, not listed on Binance yet. It had multi billion dollar valuation few years ago, it is sitting under $100m now. Few weeks ago Pocket partnered with Infura and Aave, which somehow went completely under the radar. I'm so bullish on it after I've realized that POKT can be a backbone for all of the non-blockchain projects like LLMs and AGI. Absolutely crazy...People are somehow still sleeping on it. Just my 2 cents. DYOR.

r/BitcoinSee Comment

First of all, delete these settings immediately and restart Bitcoin Core: >rpcbind=the ipv4 address shown here: https://whatismyipaddress.com/ rpcallowip=the ipv4 address shown here: https://whatismyipaddress.com/ And if you have opened that port on your router/firewall, undo that immediately. You should never expose your Bitcoin Core RPC interface to the Internet for security reasons. The only port you should forward on your router is 8333 to get incoming connections from other nodes. Here is my bitcoin.conf (I am running Bitcoin Core 25.1): `#######################` `# Application Options #` `#######################` `#assumevalid=0` `blockfilterindex=1` `coinstatsindex=1` `#dbcache=8192` `datadir=/mnt/data/bitcoin` `maxmempool=1024` `peerblockfilters=1` `peerbloomfilters=1` `txindex=1` `######################` `# Connection Options #` `######################` `bind=0.0.0.0` `bind=[::]:8333` `discover=1` `listen=1` `listenonion=1` `i2psam=127.0.0.1:7656` `maxconnections=100` `port=8333` `proxy=127.0.0.1:9050` `###############################` `# ZeroMQ Notification Options #` `###############################` `zmqpubhashblock=tcp://127.0.0.1:8433` `zmqpubrawblock=tcp://127.0.0.1:28332` `zmqpubrawtx=tcp://127.0.0.1:28333` `###########################` `# Chain Selection Options #` `###########################` `chain=main` `######################` `# Node relay options #` `######################` `mempoolfullrbf=1` `######################` `# RPC Server Options #` `######################` `rpcallowip=127.0.0.1` `rpcallowip=192.168.2.0/24` `rpcuser = username` `rpcpassword = password` `rpcbind=127.0.0.1` `rpcbind=::1` `rpcport=8332` `rpcthreads=128` `rpcworkqueue=256` `server=1` `#############################` `# Debugging/Testing options #` `#############################` `debug=i2p` `debug=tor` `shrinkdebugfile=1` If you want more info on what all those options are, you can run `bitcoind --help` and read through it. I suggest you copy and paste the output of that command in a text file so you can always keep it at hand whenever you need it. If you have specific questions about my bitcoin.conf file, feel free to ask.

Mentions:#RPC
r/CryptoCurrencySee Comment

1.I deleted my metamask account and started from scratch. 2.open metamask and clicked import account, it asked for my 12 word recovery phrase so I entered the one for my moon vault. 3.i then added the arbitrum nova network (from krakens guide) 4.i then added the moon token via the import token function 5.i could now select the arbitrum nova network and my moons would be visible 6.i then transfered some eth from my kraken 7.i then bridged the eth to the arbitrum nova network (using krakens guide) 8.the eth and moons were both visible in the arbitrum nova network 9.i tried sending the moons to kraken but the gas fees wouldn't show and when I proceeded it just said failed JSON-RPC error 10.i updated metamask still failed, I double checked network details,correct but still failed, I sent more eth for fees but still failed 11.i open my laptop and downloaded metamask to that and did step 3 to 8 again and this time the eth fees showed properly and the transaction went through

Mentions:#RPC
r/BitcoinSee Comment

To configure the JSON-RPC settings for Bitcoin Core, you need to modify the `bitcoin.conf` file, not the `settings.json` file. The `bitcoin.conf` file is located in the `.bitcoin` directory in your home folder (`/home/user/.bitcoin/`). If the `bitcoin.conf` file doesn't exist, you can create it manually. Here are the steps to configure the JSON-RPC settings: 1. Open the `bitcoin.conf` file using a text editor. 2. Add the following lines to the file: ```` rpcuser=<your_rpc_username> rpcpassword=<your_rpc_password> server=1 ``` Replace `<your_rpc_username>` and `<your_rpc_password>` with your desired username and password for JSON-RPC authentication. 3. Save the `bitcoin.conf` file. After making these changes, restart your Bitcoin Core node for the new JSON-RPC settings to take effect. --- Learn more: 1. [bitcoin/doc/JSON-RPC-interface.md at master](https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md) 2. [API reference (JSON-RPC) - Bitcoin Wiki](https://en.bitcoin.it/wiki/API_reference_(JSON-RPC)) 3. [Bitcoin.conf & JSON-RPC options - Bitcoin Stack Exchange](https://bitcoin.stackexchange.com/questions/24756/bitcoin-conf-json-rpc-options)

Mentions:#RPC#API
r/BitcoinSee Comment

You probably don't want to allow RPC (port 8332) access to the wide Internet. Core's authentication isn't especially secure. If you really want this, for your own remote access, configure your router to forward port 8332. The instructions for this vary from router to router. See http://portforward.com/. It might have your router listed in its instruction pages

Mentions:#RPC
r/CryptoCurrencySee Comment

set up ur own node! : ) even an archival node will let u broadcast ur own RPC calls

Mentions:#RPC
r/BitcoinSee Comment

also, i see here something related to the Json RPC config setup? the settings.json file under /home/user/.bitcoin/ is empty https://www.twostack.org/developer-guide/application-architecture/running-node/

Mentions:#RPC
r/BitcoinSee Comment

Ok, this is likely only semi-helpful, but perhaps it'll give some hints what to look at? I asked ChatGPT and this is the output: It appears that the user is encountering issues with their Bitcoin Core node setup, particularly with binding to ports and connecting with their Sparrow wallet. Here are a few suggestions to address the problems mentioned: ### 1. Bitcoin.conf File: It's generally recommended to use the bitcoin.conf file in the home directory, specifically `/home/user/.bitcoin/bitcoin.conf`. If you have made changes to both `/home/user/.bitcoin/bitcoin.conf` and `/root/.bitcoin/bitcoin.conf`, only the former is likely taking effect. ### 2. Port Binding: The error message indicates that Bitcoin Core is unable to bind to the specified ports because it believes another instance is already running. You can try the following steps: - Make sure Bitcoin Core is not already running. You can check running processes using `ps aux | grep bitcoind` and stop any existing instances. - Remove the `rpcport=8369` line from your `bitcoin.conf` file. The default RPC port is 8332, and changing it may not be necessary. ### 3. Check Listening Ports: The output of `sudo netstat -tulpn | grep LISTEN` shows that bitcoind is listening on port 8333. This seems fine, but you may want to ensure that no other processes are conflicting on the same ports. ### 4. Bitcoin-qt GUI Error: The error related to the Qt platform plugin suggests an issue with the graphical environment. If you are running Bitcoin Core on a headless system without a graphical interface, consider using the command-line version (`bitcoind`) rather than the GUI version (`bitcoin-qt`). ### 5. Sparrow Wallet Connection: Ensure that the Sparrow wallet is configured to connect to the correct IP address and port where your Bitcoin Core node is running. If you made changes to the RPC settings in Bitcoin Core, make sure those changes are reflected in Sparrow's configuration. ### 6. File Deletion: Regarding the mention of deleting a "sparrow" folder, it's important to be cautious. Ensure that you have a backup of important files before making any deletions. If there's no wallet in your Bitcoin Core directory, deleting a "sparrow" folder may not be relevant. ### 7. Serverless Version of Bitcoin Core: Bitcoin Core does not have a separate "serverless" version. The command-line version (`bitcoind`) can be used without a graphical interface. If you encounter issues with `bitcoin-qt`, you can rely on the command-line version for node operation. After making changes, restart your Bitcoin Core node (`bitcoind`) and Sparrow wallet to see if the issues are resolved. If problems persist, additional troubleshooting and detailed error messages may be needed to provide more specific guidance.

Mentions:#RPC
r/CryptoCurrencySee Comment

What I plan to do, I bought when it was around 20 a unit or so, and while I quite like the community and dev team I do not understand it's continued ridiculous rally. Feels overbought rn. With Moons, I felt very smart having exited $4k a week before the RPC shut down... unfortunately I also dumped the other half of my stack pretty much immediately after the announcement that crashed it ahha. I have no interested in getting back into Moons but I'm very happy a lot of the people who got rekt and held have an opportunity to cash out

Mentions:#RPC
r/CryptoCurrencySee Comment

Nothing makes me more bullish on SOL than poorly formed bearish theses. 1. TVL is down on a lot of things because of the bear market, TVL is growing on Solana faster than a lot of chains. Not sure how you thought this was an indictment in any way. Also worth mentioning that TVL is just a rudimentary way of measuring the health of a blockchain, might want to check transactions and user numbers too(spoiler alert: they're at really healthy levels). It would also make sense to check TVL on protocol to protocol basis, new protocols like Marginfi have been steadily increasing TVL. 2. "Jump crypto (Chicago firm's crypto arm) can't/won't pump more money into it like last time." This line really advertised your ignorance. "can't/won't pump more money into like last time" just means they funded Solana, which is how venture capital works. They *could* pump more money into and buy off secondary, if they wanted. Not like there would be anything wrong with that despite your implications. But regardless, they are still dedicated to improving Solana and the fact that they are building Firedancer is just proof of that. Oh and your assertion that a broader client base would somehow be a negative for Solana... well that sentiment isn't shared by anyone in crypto... https://jumpcrypto.com/firedancer/ (already on testnet) Secondly, can we stop treating VC's as if they are the illuminati? They are literally just investors, not the boogeyman. At least try to bring some proof when you want to blame everything 3. "71M SOL or 17% of circulating supply and that's a ton of SOL to dump any way you slice and spin it..." Yeah and every other coin on the market has people that will sell too. If you want to avoid an asset because of a single entities forced liquidation, which is going to be executed in a way that minimizes market impact, go for it. But you're not even going to notice it. They've already been selling 250,000-750,000 SOL per day and obviously it hasn't done anything. ([source](https://x.com/Bluntz_Capital/status/1722414938768146583?s=20)) 4. Applies to literally every coin not named Ethereum. 5. "Between January 2022 and February 2023, Solana had occasions in 7 out of those 13 months with outages." That's wrong, their were only 3 outages. Check status.solana.com/history and be sure not to confuse performance degradations with outages. Every chain has occasional hiccups that they typically lable as "Performance Degradation" where certain operations won't work as intended but the chain remains operational. Eg. not finalizing txn's, RPC's being down so your txn's never get submitted, assorted issues leading to higher levels of failed, reorgs, etc.

Mentions:#SOL#VC#RPC
r/CryptoCurrencySee Comment

Hi, is that guide possibly out of date? I’ve followed it but getting a notification once I’ve tried adding the network that they can’t find the chain ID and it’s asking if the RPC url is correct (which I’ve copied exactly)

Mentions:#RPC
r/CryptoCurrencySee Comment

Ethereum Layer 2 activity update for the past week, via [L2beat.com](https://l2beat.com/scaling/activity): |||||||| |:-|:-|:-|:-|:-|:-|:-| |\#|Name|Past day TPS|7d Change|Max daily TPS|30D Count|Data source| |1|Ethereum|13.27|\+3.76%|22.37on 2022 Dec 09|31.33 M|Blockchain RPC| |2|Arbitrum One|8.62|\+3.11%|31.64on 2023 Mar 23|17.84 M|Blockchain RPC| |3|dYdX|5.88|\+28.64%|11.45on 2022 Feb 15|9.05 M|Closed API| |4|zkSync Era|4.05|\-47.36%|15.25on 2023 Aug 26|21.79 M|Blockchain RPC| |5|OP Mainnet|3.52|\+16.04%|10.43on 2023 Jul 27|7.77 M|Blockchain RPC| |6|Immutable X|2.69|\+2.92%|39.35on 2022 Mar 11|7.08 M|Closed API| |7|Base|2.12|\-26.38%|21.29on 2023 Sep 14|9.57 M|Blockchain RPC| |8|Mantle|1.98|\-15.97%|4.41on 2023 Oct 15|6.26 M|Blockchain RPC| |9|Arbitrum Nova|1.83|\-5.43%|10.93on 2023 Apr 27|5.49 M|Blockchain RPC| |10|Starknet|1.58|\-66.86%|10.16on 2023 Sep 09|12.60 M|Blockchain RPC| |11|ApeX|1.41|\+9.11%|1.90on 2023 Sep 27|3.25 M|Closed API| |12|Linea|1.40|\+41.68%|4.21on 2023 Oct 09|3.46 M|Blockchain RPC| |13|Scroll|1.03|\-56.35%|5.03on 2023 Nov 09|4.32 M|Blockchain RPC| |14|Sorare|0.80|\+21.06%|2.31on 2022 Oct 23|1.31 M|Closed API| |15|Polygon zkEVM|0.51|\-13.38%|1.41on 2023 Aug 04|1.15 M|Blockchain RPC| |16|rhino.fi|0.49|\-21.65%|1.71on 2023 Nov 09|1.23 M|Closed API| |17|Manta Pacific|0.44|\+30.99%|0.52on 2023 Oct 17|869 K|Blockchain RPC| |18|Zora|0.42|\-16.78%|1.63on 2023 Aug 17|1.56 M|Blockchain RPC| |19|Metis Andromeda|0.21|\+28.06%|1.25on 2022 Mar 12|372 K|Blockchain RPC| |20|zkSync Lite|0.20|\-45.26%|3.29on 2023 Mar 21|1.16 M|Explorer API| The two big gainers this week were dYdX and OP. Ethereum mainnet also saw a healthy gain of 3% in its transaction volume.

Mentions:#RPC#API#OP
r/CryptoCurrencySee Comment

Full nodes fully verify the chain; they store the current state of the blockchain, including all accounts, balances, storage, and contract code. You can currently run NiceNode on your Ubuntu, run a full node, and point your Metamask to the RPC so you can send transactions. Difficulty bomb also doesn't exist since the merge. You really need to do your own research instead of listening to Bitcoin maxis talk about Ethereum. Like, why would I rely on Ethereum influencers for information on Bitcoin? Makes no sense. Don't trust, verify.

Mentions:#RPC
r/CryptoCurrencySee Comment

Don't you understand what is happening with LINK? Eth is becoming just another chain in a multichain world, besides, lots of people have taken a step back from ETH now it's become clear that scalability is only being addressed by L2s (which, besides being centralized, can be used on ANY chain), and are also seeing that ETH's move to PoS made it more centralized if anything, JPMorgan buying up Infura (the main ETH RPC), LIDO basically controlling most of the validators... Meanwhile there are new projects out there revolutionizing decentralized consensus and scalability

Mentions:#LINK#ETH#RPC
r/CryptoCurrencySee Comment

You need to import moons token onto MetaMask. Hope this helps A Beginner’s Guide to Trading and Sending MOONs Hi everyone, Yesterday, I was searching around for how to trade and swap my MOONs and couldn’t find a decent instructions on how the to do this and I could see how so many people might find the process confusing. So below I’ve created a Step-by-Step guide on how to do this: **1) How do I know if I have any MOONs?** 1. Check your comments or posts on r/CryptoCurrency to see your profile MOON count. 2. Search your Vault Wallet address on the [Arbitrum Nova Block Explorer](https://nova.arbiscan.io/) 3. Check on [CCMoons](https://ccmoons.com/estimator) to see your estimated karma you’ll be distributed. **2) Setting up MetaMask** *On your mobile or desktop:* 1. Install [Metamask](https://metamask.io/) 2. Import your seed phrase of your Vault. Please keep in mind that these 12 words are like your bank card and code, so **NEVER** share this with someone. 3. Your Vault can only be found in the Reddit app, when you are in your Vault, click on the three dots above. Click on 'recovery phrase' for the 12 words of your wallet. **3) Adding Arbitrum Nova** 1. Click ‘*Networks*’ and then proceed to click ‘*Add a network*’ and go to ‘*custom networks*’. 2. Type in the following details to the available text-boxes displayed: Network Name: Arbitrum Nova RPC Url: [https://nova.arbitrum.io/rpc](https://nova.arbitrum.io/rpc) Chain ID: 42170 Symbol : ETH Block Explorer URL: [https://nova.arbiscan.io](https://nova.arbiscan.io/) **4) Importing the token (MOONs)** 1. Click ‘*Import Tokens*’ on the main section 2. Type in the following details to the available text-boxes displayed: Token Address: 0x0057Ac2d777797d31CD3f8f13bF5e927571D6Ad0 Token Symbol: MOON Token Decimal: 18 **5) Sending and Receiving MOONs** 1. Open your Vault and click on the paper-aeroplane icon, write the desired amount and relevant username and send. **OR** 2. Open MetaMask, click ‘*Send*’ and enter recipients address, enter the amount you’d like to send and select MOONs. Click ‘*next*’ and proceed to ‘*Send*’. **6) Swapping MOONs on SushiSwap** 1. Open [SushiSwap](https://www.sushi.com/swap) on the MetaMask browser (or another safe browser). 2. Connect your wallet and ensure your MetaMask wallet is on the Arbitrum Nova Network (on both MetaMask and SushiSwap) 3. Selected MOONs from the drop-down list of token/coin options (and which one you’d like to swap for) and enter the amount you wish to trade with. 4. Click SWAP and confirm the transaction and wait a couple of seconds and everything should all be completed. **7) What if I can’t pay for gas fees?** 1. Go check out this Reddit bot faucet thread [here](https://www.reddit.com/r/CryptoCurrencyMoons/comments/yxb3vn/arbitrum_nova_eth_and_polygon_matic_reddit_bot/?utm_source=share&utm_medium=ios_app&utm_name=iossmf) and comment ‘ !gas nova ’. **If you are able donate some ETH to the bot, that would be great.** **8) Thanks for Reading!** I hope this has helped at least one person and feel free to comment any edits I should make to the post. ⚠️ **Disclaimer: swapping and selling more than 25% of your earned MOONs affects your karma multiplier, shown** [here](https://www.reddit.com/r/CryptoCurrency/comments/u3js8m/ccip_030_create_karma_multiplier_based_on_moon/?utm_source=share&utm_medium=ios_app&utm_name=iossmf)⚠️ 👍 credit to u/ominous_anenome for creating [CCMoons](https://ccmoons.com/)👍

Mentions:#RPC#ETH#SWAP
r/BitcoinSee Comment

Through the RPC interface (or debug console in the GUI) you can dump all transactions. Warning: be very careful with entering *any* commands at all, including the ones I suggest below, in RPC or the debug console. For starters make sure you understand what they do, e.g. by looking them up in https://bitcoincore.org/en/doc/25.0.0/ or other sources. Bad commands can reveal private keys, and send or destroy funds. Try `getblock 00000000000000000007316856900e76b4f7a9139cfbfba89842c8d196cd5f91 2`. It will show all transactions in that block (which is block #600000 in the main chain), with some level of detail. If you have the `txindex` feature enabled, you can also look for individual transactions using the `getrawtransaction` command by txid.

Mentions:#RPC
r/BitcoinSee Comment

> without an API You have to use an API. There is no guarantee that the blocks are stored in the BLK0nnnn.dat files in order. You could run without an API if you copy all the "where is this block?" logic built into Core, which also ignores fragments of REV data. But the Bitcoin RPC API has options to send you a hexadecimal representation of the block, which you can then convert to binary and process according to the block layout in the dev site I think that's what you're looking for. You really don't want to be concerned with out-of-order blocks and REV data fragments Use the *getblock* RPC with verbosity 0. For example, block 815506 bitcoin-cli getblock 0000000000000000000393fa0584c84f9d51af58901d0f0de96a31e21dae6098 0 If you just want the block header in hex bitcoin-cli getblockheader 0000000000000000000393fa0584c84f9d51af58901d0f0de96a31e21dae6098 false > difficulty Difficulty is irrelevant to Bitcoin processing. Difficulty is a made-up number derived from target. A block header hash is valid if it is smaller than target. The proof of work is that there have been enough guesses when a miner constructs a block which has a header which has a hash which is smaller than target. Target is adjusted smaller to make mining harder, and vice versa, in response to the actual block interval being faster or slower than 10 minutes > bits A Bitcoin-specific number representation which squeezes a 256-bit target hash into a 32-bit field. Antonopoulos describes the format https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch10.asciidoc Search down to "Target Representation" *bits* is a 32-bit field. The first 8 bits contains an exponent (or a byte count). The other 24 bits are a coefficient or mantissa, for precision. This means that even though we're squeezing a 256 bit target into 32 bits, we have 24 bits of precision to play with, way more than necessary for each target adjustment. The coefficient provides precision and the exponent provides gross size. The exponent is a count of the number of bytes of the coefficient (3 bytes) plus all the trailing zeros Here's the block header for 815506 00c0c223a1e0de4f69777a80c73ece7ff5ef92763ca6fed19393000000000000000000004f6299f8eeeb4451e0185480a6378f33be42d6762e0468dd34e54800b65745f84a1a486594810417204ccadf *bits* begins at byte 73 94810417 Inconveniently, it's in reverse byte order (backwards). Reverse the bytes 17048194 The exponent is 0x17 and the coefficient is 0x048194. The 256-bit hexadecimal representation of the target is 048194 followed by 20 zero-bytes - total length 23 bytes (0x17) 0481940000000000000000000000000000000000000000 Mathematically 0x048194 * 0x100 ^ (0x17 - 3) Difficultly was arbitrarily defined as equal to 1 during the initial mining phase. Target adjustment is coded so that it can never be higher than the initial target *0x1d00ffff* To calculate difficulty difficulty = difficulty_1_target / current_target Calculate difficulty for 815506 0x00FFFF0000000000000000000000000000000000000000000000000000 / 0x0481940000000000000000000000000000000000000000 = 62463471666732.7234

r/CryptoCurrencySee Comment

If you want to learn more about blockchain security a 'learn by doing' idea would be to run a node. As far as I know the 3 L1s where this is possible on cheap hardware are Bitcoin, Ethereum and Cardano. If you run an Ethereum node you can also run L2 nodes (e.g. Arbitrum, Optimism, Starknet, ...). My suggestion would be to go the Ethereum (and an L2) route. Getting ready to do this will teach you about the modular blockchain model and client diversity as the Ethereum chain runs as two linked parts, Execution (where all the transactions take place) and Consensus (where staking and attesting to blocks happens). In order to run an Ethereum node you must run an Execution client and a Consensus client together. Where Ethereum's security and decentralization come in to play is the fact that there are about 5 of each type of client to choose from, meaning 25 different possibilities of combinations. The clients are all made by different teams, in different countries, and built in different programming languages. This means that if there is a bug in one client it is almost impossibly unlikely to also occur in the others. The network can keep going in the event of one or some of the clients breaking, and so is extremely resilient to both accidental bugs or intentional attack. Once you've got your node running you can start using it. The easiest first step is to connect your wallet to it, replacing the default RPC with your local node. This means your transactions are broadcast directly to Ethereum rather than going through a 3rd party connection like Infura. This has 2 benefits, you will always be able to access the chain, regardless of any other infrastructure being temporarily down, and you regain some privacy of transactions. Once that's all running you can start getting into some simple programming, using the Python library web3.py for example which will let you do stuff like querying balances for accounts directly without relying on blockchain explorers like Etherscan; looking up addresses by their ENS names etc etc. Then you'll have gained a pretty decent practical knowledge of how the chain works and can start playing with whatever you fancy next. The possibilities really are endless and whatever grabs your interest will be another opportunity to learn.

Mentions:#RPC#ENS
r/BitcoinSee Comment

> The gettransaction RPC now returns a lastprocessedblock JSON object which contains the wallet's last processed block hash and height at the time the transaction information was generated. (#26094) > > The getwalletinfo RPC now returns a lastprocessedblock JSON object which contains the wallet's last processed block hash and height at the time the wallet information was generated. (#26094) > > Coin selection and transaction building now accounts for unconfirmed low-feerate ancestor transactions. When it is necessary to spend unconfirmed outputs, the wallet will add fees to ensure that the new transaction with its ancestors will achieve a mining score equal to the feerate requested by the user. (#26152) > > For RPC methods which accept options parameters ((importmulti, listunspent, fundrawtransaction, bumpfee, send, sendall, walletcreatefundedpsbt, simulaterawtransaction), it is now possible to pass the options as named parameters without the need for a nested object. (#26485) > > This means it is possible make calls like: > > src/bitcoin-cli -named bumpfee txid fee_rate=100 > instead of > > src/bitcoin-cli -named bumpfee txid options='{"fee_rate": 100}' > The deprecatedrpc=walletwarningfield configuration option has been removed. The createwallet, loadwallet, restorewallet and unloadwallet RPCs no longer return the "warning" string field. The same information is provided through the "warnings" field added in v25.0, which returns a JSON array of strings. The "warning" string field was deprecated also in v25.0. (#27757) > > The signrawtransactionwithkey, signrawtransactionwithwallet, walletprocesspsbt and descriptorprocesspsbt calls now return the more specific RPC_INVALID_PARAMETER error instead of RPC_MISC_ERROR if their sighashtype argument is malformed. (#28113) > > RPC walletprocesspsbt, and descriptorprocesspsbt return object now includes field hex (if the transaction is complete) containing the serialized transaction suitable for RPC sendrawtransaction. (#28414) > > GUI changes > Low-level changes > RPC > Tests > Non-standard transactions are now disabled by default on testnet for relay and mempool acceptance. The previous behaviour can be re-enabled by setting -acceptnonstdtxn=1. (#28354) > Credits > Thanks to everyone who directly contributed to this release: > > 0xb10c > Amiti Uttarwar > Andrew Chow > Andrew Toth > Anthony Towns > Antoine Poinsot > Antoine Riard > Ari > Aurèle Oulès > Ayush Singh > Ben Woosley > Brandon Odiwuor > Brotcrunsher > brunoerg > Bufo > Carl Dong > Casey Carter > Cory Fields > David Álvarez Rosa > dergoegge > dhruv > dimitaracev > Erik Arvstedt > Erik McKelvey > Fabian Jahr > furszy > glozow > Greg Sanders > Harris > Hennadii Stepanov > Hernan Marino > ishaanam > ismaelsadeeq > Jake Rawsthorne > James O'Beirne > John Moffett > Jon Atack > josibake > kevkevin > Kiminuo > Larry Ruane > Luke Dashjr > MarcoFalke > Marnix > Martin Leitner-Ankerl > Martin Zumsande > Matthew Zipkin > Michael Ford > Michael Tidwell > mruddy > Murch > ns-xvrn > pablomartin4btc > Pieter Wuille > Reese Russell > Rhythm Garg > Ryan Ofsky > Sebastian Falbesoner > Sjors Provoost > stickies-v > stratospher > Suhas Daftuar > TheCharlatan > Tim Neubauer > Tim Ruffing > Vasil Dimov > virtu > vuittont60 > willcl-ark > Yusuf Sahin HAMZA > As well as to everyone that helped with translations on Transifex.

Mentions:#RPC
r/BitcoinSee Comment

This one is going to have support for BIP324, wow lad. > The release notes draft is a temporary file that can be added to by anyone. See /doc/developer-notes.md#release-notes for the process. > > 26.0 Release Notes Draft > Bitcoin Core version 26.0 is now available from: > > https://bitcoincore.org/bin/bitcoin-core-26.0/ > > This release includes new features, various bug fixes and performance improvements, as well as updated translations. > > Please report bugs using the issue tracker at GitHub: > > https://github.com/bitcoin/bitcoin/issues > > To receive security and update notifications, please subscribe to: > > https://bitcoincore.org/en/list/announcements/join/ > > How to Upgrade > If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes in some cases), then run the installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on macOS) or bitcoind/bitcoin-qt (on Linux). > > Upgrading directly from a version of Bitcoin Core that has reached its EOL is possible, but it might take some time if the data directory needs to be migrated. Old wallet versions of Bitcoin Core are generally supported. > > Compatibility > Bitcoin Core is supported and extensively tested on operating systems using the Linux kernel, macOS 11.0+, and Windows 7 and newer. Bitcoin Core should also work on most other Unix-like systems but is not as frequently tested on them. It is not recommended to use Bitcoin Core on unsupported systems. > > Notable changes > P2P and network changes > Experimental support for the v2 transport protocol defined in BIP324 was added. It is off by default, but when enabled using -v2transport it will be negotiated on a per-connection basis with other peers that support it too. The existing v1 transport protocol remains fully supported. > > Nodes with multiple reachable networks will actively try to have at least one outbound connection to each network. This improves individual resistance to eclipse attacks and network level resistance to partition attacks. Users no longer need to perform active measures to ensure being connected to multiple enabled networks. (#27213) > > Pruning > When using assumeutxo with -prune, the prune budget may be exceeded if it is set lower than 1100MB (i.e. MIN_DISK_SPACE_FOR_BLOCK_FILES * 2). Prune budget is normally split evenly across each chainstate, unless the resulting prune budget per chainstate is beneath MIN_DISK_SPACE_FOR_BLOCK_FILES in which case that value will be used. (#27596) > Updated RPCs > Setting -rpcserialversion=0 is deprecated and will be removed in a future release. It can currently still be used by also adding the -deprecatedrpc=serialversion option. (#28448) > > The hash_serialized_2 value has been removed from gettxoutsetinfo since the value it calculated contained a bug and did not take all data into account. It is superseded by hash_serialized_3 which provides the same functionality but serves the correctly calculated hash. (#28685) > > New fields transport_protocol_type and session_id were added to the getpeerinfo RPC to indicate whether the v2 transport protocol is in use, and if so, what the session id is. > > A new argument v2transport was added to the addnode RPC to indicate whether a v2 transaction connection is to be attempted with the peer. > > Changes to wallet related RPCs can be found in the Wallet section below. > > New RPCs > loadtxoutset has been added, which allows loading a UTXO snapshot of the format generated by dumptxoutset. Once this snapshot is loaded, its contents will be deserialized into a second chainstate data structure, which is then used to sync to the network's tip. > > Meanwhile, the original chainstate will complete the initial block download process in the background, eventually validating up to the block that the snapshot is based upon. > > The result is a usable bitcoind instance that is current with the network tip in a matter of minutes rather than hours. UTXO snapshot are typically obtained via third-party sources (HTTP, torrent, etc.) which is reasonable since their contents are always checked by hash. > > You can find more information on this process in the assumeutxo design document (https://github.com/bitcoin/bitcoin/blob/master/doc/design/assumeutxo.md). > > getchainstates has been added to aid in monitoring the assumeutxo sync process. > > A new getprioritisedtransactions RPC has been added. It returns a map of all fee deltas created by the user with prioritisetransaction, indexed by txid. The map also indicates whether each transaction is present in the mempool. (#27501) > > A new RPC, submitpackage, has been added. It can be used to submit a list of raw hex transactions to the mempool to be evaluated as a package using consensus and mempool policy rules. These policies include package CPFP, allowing a child with high fees to bump a parent below the mempool minimum feerate (but not minimum relay feerate). (#27609) > > Warning: successful submission does not mean the transactions will propagate throughout the network, as package relay is not supported. > > Not all features are available. The package is limited to a child with all of its unconfirmed parents, and no parent may spend the output of another parent. Also, package RBF is not supported. Refer to doc/policy/packages.md for more details on package policies and limitations. > > This RPC is experimental. Its interface may change. > > A new RPC getaddrmaninfo has been added to view the distribution of addresses in the new and tried table of the node's address manager across different networks(ipv4, ipv6, onion, i2p, cjdns). The RPC returns count of addresses in new and tried table as well as their sum for all networks. (#27511) > > A new importmempool RPC has been added. It loads a valid mempool.dat file and attempts to add its contents to the mempool. This can be useful to import mempool data from another node without having to modify the datadir contents and without having to restart the node. (#27460) > > Warning: Importing untrusted files is dangerous, especially if metadata from the file is taken over. > If you want to apply fee deltas, it is recommended to use the getprioritisedtransactions and prioritisetransaction RPCs instead of the apply_fee_delta_priority option to avoid double-prioritising any already-prioritised transactions in the mempool. > Build System > Updated settings > bitcoind and bitcoin-qt will now raise an error on startup if a datadir that is being used contains a bitcoin.conf file that will be ignored, which can happen when a datadir= line is used in a bitcoin.conf file. The error message is just a diagnostic intended to prevent accidental misconfiguration, and it can be disabled to restore the previous behavior of using the datadir while ignoring the bitcoin.conf contained in it. (#27302) > > Passing an invalid -debug, -debugexclude, or -loglevel logging configuration option now raises an error, rather than logging an easily missed warning. (#27632) > > Changes to GUI or wallet related settings can be found in the GUI or Wallet section below. > > New settings > Tools and Utilities > A new bitcoinconsensus_verify_script_with_spent_outputs function is available in libconsensus which optionally accepts the spent outputs of the transaction being verified. > A new bitcoinconsensus_SCRIPT_FLAGS_VERIFY_TAPROOT flag is available in libconsensus that will verify scripts with the Taproot spending rules. > Wallet > Wallet loading has changed in this release. Wallets with some corrupted records that could be previously loaded (with warnings) may no longer load. For example, wallets with corrupted address book entries may no longer load. If this happens, it is recommended load the wallet in a previous version of Bitcoin Core and import the data into a new wallet. Please also report an issue to help improve the software and make wallet loading more robust in these cases. (#24914) > > The gettransaction, listtransactions, listsinceblock RPCs now return the abandoned field for all transactions. Previously, the "abandoned" field was only returned for sent transactions. (#25158) > > The listdescriptors, decodepsbt and similar RPC methods now show h rather than apostrophe (') to indicate hardened derivation. This does not apply when using the private parameter, which matches the marker used when descriptor was generated or imported. Newly created wallets use h. This change makes it easier to handle descriptor strings manually. E.g. the importdescriptors RPC call is easiest to use h as the marker: '["desc": ".../0h/..."]'. With this change listdescriptors will use h, so you can copy-paste the result, without having to add escape characters or switch ' to 'h' manually. Note that this changes the descriptor checksum. For legacy wallets the hdkeypath field in getaddressinfo is unchanged, nor is the serialization format of wallet dumps. (#26076) > > The getbalances RPC now returns a lastprocessedblock JSON object which contains the wallet's last processed block hash and height at the time the balances were calculated. This result shouldn't be cached because importing new keys could invalidate it. (#26094) >

r/CryptoMarketsSee Comment

Pocket team is making smart moves that will pay off in the bull market when the development activity reaches new ATH. Almost all builders in crypto space need decentralized RPC and decentralized infra. Potential is limitless.

Mentions:#RPC
r/CryptoCurrencySee Comment

Do you have to work at being so incompetent or does it come naturally? 1)September 14, 2021: Down for 17 hours 12 minutes due to a DDoS attack on a decentralised exchange(DEX). 2)January 6 – 8, 2022: Outage for multiple days. Presumably DDoS attack. 3)January 10, 2022: Assumed to be the same DDoS attack. January 22, 2022: 29 hours of downtime, lots of duplicate transactions causing congestion and outages. 4)March 28, 2022: RPC nodes forked off when upgrade to v1.9 happened. 5)April 30, 2022: seven hour outage due to network experienced interruptions and down time. 6)September 14, 2021: Down for 17 hours 12 minutes due to a DDoS attack on a decentralised exchange(DEX). 7)January 6 – 8, 2022: Outage for multiple days. Presumably DDoS attack. 8)January 10, 2022: Assumed to be the same DDoS attack. 9)January 22, 2022: 29 hours of downtime, lots of duplicate transactions causing congestion and outages. 10)March 28, 2022: RPC nodes forked off when upgrade to v1.9 happened. 11)April 30, 2022: seven hour outage due to millions of NFTs being minted. 12)May 27, 2022: Block times delayed up to 30 minutes. 13)June 1, 2022: “A runtime bug triggered by the durable nonce transactions feature allowed, under a specific set of circumstances, for a failed durable nonce transaction to be processed twice.” Lasted about 5 hours. 14)October 1, 2022: A misconfigured node resulted in lost data and needs to restart from a previous point, which apparently crashes the entire chain. 15)February 28, 2023: “Solana Mainnet is experiencing a large forking event right now, validators are investigating to determine the network health, root cause and next steps. Transactions may fail right now”. Lasted for about 20 hours. millions of NFTs being minted. 16)May 27, 2022: Block times delayed up to 30 minutes. 17)June 1, 2022: “A runtime bug triggered by the durable nonce transactions feature allowed, under a specific set of circumstances, for a failed durable nonce transaction to be processed twice.” Lasted about 5 hours. 18)October 1, 2022: A misconfigured node resulted in lost data and needs to restart from a previous point, which apparently crashes the entire chain. 19)February 28, 2023: “Solana Mainnet is experiencing a large forking event right now, validators are investigating to determine the network health, root cause and next steps. Transactions may fail right now”. Lasted for about 20 hours.

Mentions:#DEX#RPC
r/CryptoCurrencySee Comment

[latitude.sh](https://latitude.sh) rents those out :). It's a 7443p with 1TB RAM. For RPC queries.

Mentions:#RAM#RPC
r/CryptoCurrencySee Comment

Ethereum L2 activity update for the last week: |||||||| |:-|:-|:-|:-|:-|:-|:-| |\#|Name|Past day TPS|7d Change|Max daily TPS|30D Count|Data source| |1|Ethereum|12.61|\-0.79%|22.37on 2022 Dec 09|30.42 M|Blockchain RPC| |2|zkSync Era|7.61|\+28.81%|15.25on 2023 Aug 26|24.93 M|Blockchain RPC| |3|Arbitrum One|7.30|\-17.95%|31.64on 2023 Mar 23|16.76 M|Blockchain RPC| |4|Starknet|4.71|\+91.90%|10.16on 2023 Sep 09|14.46 M|Blockchain RPC| |5|dYdX|3.60|\-43.14%|11.45on 2022 Feb 15|7.17 M|Closed API| |6|Base|3.03|\-14.45%|21.29on 2023 Sep 14|14.00 M|Blockchain RPC| |7|Immutable X|2.70|\+33.97%|39.35on 2022 Mar 11|6.46 M|Closed API| |8|OP Mainnet|2.50|\-31.13%|10.43on 2023 Jul 27|7.22 M|Blockchain RPC| |9|Mantle|2.17|\+9.22%|4.41on 2023 Oct 15|7.08 M|Blockchain RPC| |10|Scroll|2.08|\+207.81%|2.35on 2023 Oct 29|1.79 M|Blockchain RPC| |11|Arbitrum Nova|2.03|\-15.04%|10.93on 2023 Apr 27|5.24 M|Blockchain RPC| |12|ApeX|1.29|\-28.46%|1.90on 2023 Sep 27|2.96 M|Closed API| |13|Linea|1.01|\+21.83%|4.21on 2023 Oct 09|4.84 M|Blockchain RPC| |14|Sorare|0.80|\-0.03%|2.31on 2022 Oct 23|1.28 M|Closed API| |15|rhino.fi|0.72|\+480.14%|0.77on 2023 Oct 30|441 K|Closed API| |16|Zora|0.48|\+10.44%|1.63on 2023 Aug 17|2.06 M|Blockchain RPC| |17|Polygon zkEVM|0.38|\+34.96%|1.41on 2023 Aug 04|916 K|Blockchain RPC| |18|zkSync Lite|0.38|\+11.59%|3.29on 2023 Mar 21|1.41 M|Explorer API| |19|Manta Pacific|0.25|\-18.23%|0.52on 2023 Oct 17|633 K|Blockchain RPC| |20|Metis Andromeda|0.13|\-33.99%|1.25on 2022 Mar 12|333 K|Blockchain RPC| via [https://l2beat.com/scaling/activity](https://l2beat.com/scaling/activity) StarkNet, Scroll and rhino.fi are the standouts this week. Polygon zkEVM also had a respectable showing.

Mentions:#RPC#API#OP
r/CryptoCurrencySee Comment

tldr; Solana has announced a new milestone in blockchain accessibility by deploying nodes on Amazon Web Services (AWS) through the Node Runner app. This integration with AWS Cloud's Node Runner App makes Solana the second blockchain, after Ethereum, to be supported by AWS. The deployment of Solana nodes on AWS allows for seamless deployment of consensus and RPC nodes, making it easier for enterprises to connect their decentralized applications (dApps) to the Solana network. This collaboration between Solana and AWS Cloud is a significant step towards making blockchain technology more accessible and user-friendly, potentially improving the Solana ecosystem and advancing the widespread adoption of decentralized technologies. *This summary is auto generated by a bot and not meant to replace reading the original article. As always, DYOR.

Mentions:#RPC#DYOR
r/CryptoCurrencySee Comment

Reddit pulled the plug off all RPC’s

Mentions:#RPC