RPC

px403

The TORN network was a completely separate thing that was basically a prototype for early decentralized account abstraction, and it didn't even exist when Lazarus put money in Tornado, which is basically what's got the prosecutors all hot and bothered. The TORN network basically let anyone stake a bunch of TORN so they could run a node. Anyone could connect to any of the TORN nodes and send them a signed transaction, which would then get submitted by the TORN node in exchange for a small fee. From what I've heard, that network wasn't even being used by criminals, especially North Korea, who will just run their own Ethereum RPC nodes or whatever. It's just a nice privacy layer so people don't need to submit transactions via Metamask/Infura. What's wild is that he wasn't even running a TORN node or anything, he just got a cut of the initial TORN distribution, but it was argued that if criminals started using the TORN network, then the value of the token might go up, so in a weird ass-backwords hypothetical scenario, he might indirectly see some profits from criminal activity. Fucking wild.

aminok

Ethereum Layer 2 activity over the last week: | | | | | | | | | | :-: | :-: | :-: | :-: | :-: | :-: | :-: | :-: | | # | | Name | Past day TPS | 7d Change | Max daily TPS | 30D Count | Data source | | 1 | | Arbitrum One | 25.14 | +43.80% | 58.97on 2023 Dec 16 | 50.08 M | Blockchain RPC | | 2 | | Base | 23.10 | -18.63% | 36.99on 2024 Apr 08 | 74.66 M | Blockchain RPC | | 3 | | Ethereum | 13.46 | -2.28% | 22.70on 2024 Jan 14 | 35.22 M | Blockchain RPC | | 4 | | zkSync Era | 9.05 | -16.96% | 62.07on 2023 Dec 16 | 29.46 M | Blockchain RPC | | 5 | | Blast | 6.67 | -21.82% | 9.40on 2024 Mar 01 | 15.85 M | Blockchain RPC | | 6 | | OP Mainnet | 5.92 | -7.86% | 11.29on 2024 Mar 27 | 17.98 M | Blockchain RPC | | 7 | | Arbitrum Nova | 4.45 | +193.46% | 54.90on 2024 Mar 05 | 9.81 M | Blockchain RPC | | 8 | | Linea | 4.22 | -25.15% | 55.70on 2024 Mar 31 | 11.69 M | Blockchain RPC | | 9 | | Scroll | 3.98 | -6.82% | 6.50on 2024 May 09 | 10.24 M | Blockchain RPC | | 10 | | Mantle | 3.31 | -16.65% | 25.47on 2023 Dec 27 | 9.57 M | Blockchain RPC | | 11 | | Immutable X | 2.45 | +9.63% | 39.35on 2022 Mar 11 | 7.72 M | Closed API | | 12 | | Mode Network | 2.31 | -0.56% | 6.03on 2024 May 07 | 6.65 M | Blockchain RPC | | 13 | | ApeX | 1.83 | -5.76% | 3.24on 2024 Feb 22 | 4.81 M | Closed API | | 14 | | Zora | 1.26 | +13.64% | 12.81on 2024 Apr 09 | 6.48 M | Blockchain RPC | | 15 | | Starknet | 1.16 | +1.25% | 12.30on 2024 Feb 20 | 2.68 M | Blockchain RPC | | 16 | | dYdX v3 | 0.98 | -17.14% | 11.45on 2022 Feb 15 | 2.79 M | Closed API | | 17 | | Redstone | 0.71 | -16.63% | 2.85on 2024 May 02 | 1.55 M | Blockchain RPC | | 18 | | Manta Pacific | 0.69 | -22.09% | 5.88on 2023 Dec 22 | 1.98 M | Blockchain RPC | | 19 | | tanX | 0.65 | +0.00% | 1.22on 2024 Feb 18 | 1.60 M | Closed API | | 20 | | X Layer | 0.58 | -4.17% | 4.72on 2024 Apr 16 | 1.80 M | Blockchain RPC | source: https://l2beat.com/scaling/activity

stryker7314

Even better, I turned off prune so I can store the full blockchain. I enabled RPC but not sure what that's even gonna do even after reading about it I'm confused lol.

ma0za

No bud. Just no. Below are the Network & Hardware reqs for a rpc node. Source: https://docs.solanalabs.com/de/operations/requirements Networking: Internet service should be at least 1GBbit/s symmetric, commercial. 10GBit/s preferred. Hardware Recommendations The hardware recommendations below are provided as a guide. Operators are encouraged to do their own performance testing. CPU 12 cores / 24 threads, or more 2.8GHz base clock speed, or faster SHA extensions instruction support AMD Gen 3 or newer Intel Ice Lake or newer AVX2 instruction support (to use official release binaries, self-compile otherwise) Support for AVX512f is helpful RAM 256GB or more Error Correction Code (ECC) memory is suggested Motherboard with 512GB capacity suggested Disk PCIe Gen3 x4 NVME SSD, or better Accounts: 500GB, or larger. High TBW (Total Bytes Written) Ledger: 1TB or larger. High TBW suggested OS: (Optional) 500GB, or larger. SATA OK The OS may be installed on the ledger disk, though testing has shown better performance with the ledger on its own disk Accounts and ledger can be stored on the same disk, however due to high IOPS, this is not recommended The Samsung 970 and 980 Pro series SSDs are popular with the validator community GPUs Not necessary at this time Operators in the validator community do no use GPUs currently RPC Node Recommendations The hardware recommendations above should be considered bare minimums if the validator is intended to be employed as an RPC node. To provide full functionality and improved reliability, the following adjustments should be made. CPU 16 cores / 32 threads, or more RAM 512 GB or more if account-index is used Disk Consider a larger ledger disk if longer transaction history is required Accounts and ledger should not be stored on the same disk

HSuke

Do any explorers on any blockchains allow this? That's really expensive even for slower blockchains. Just run a full node, or pay for RPC access.

ma0za

Source: https://docs.solanalabs.com/de/operations/requirements Hardware Recommendations The hardware recommendations below are provided as a guide. Operators are encouraged to do their own performance testing. CPU 12 cores / 24 threads, or more 2.8GHz base clock speed, or faster SHA extensions instruction support AMD Gen 3 or newer Intel Ice Lake or newer AVX2 instruction support (to use official release binaries, self-compile otherwise) Support for AVX512f is helpful RAM 256GB or more Error Correction Code (ECC) memory is suggested Motherboard with 512GB capacity suggested Disk PCIe Gen3 x4 NVME SSD, or better Accounts: 500GB, or larger. High TBW (Total Bytes Written) Ledger: 1TB or larger. High TBW suggested OS: (Optional) 500GB, or larger. SATA OK The OS may be installed on the ledger disk, though testing has shown better performance with the ledger on its own disk Accounts and ledger can be stored on the same disk, however due to high IOPS, this is not recommended The Samsung 970 and 980 Pro series SSDs are popular with the validator community GPUs Not necessary at this time Operators in the validator community do no use GPUs currently RPC Node Recommendations The hardware recommendations above should be considered bare minimums if the validator is intended to be employed as an RPC node. To provide full functionality and improved reliability, the following adjustments should be made. CPU 16 cores / 32 threads, or more RAM 512 GB or more if account-index is used Disk Consider a larger ledger disk if longer transaction history is required Accounts and ledger should not be stored on the same disk

timbulance

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 our support team

bieker

The transaction details in the block you are mining are relevant. So every time someone else mines a block you have to start over, also the nonce is only 4 bytes, so you can only do 3.8B hashes on it before you need to change something else in it. Assembling a block to mine is pretty easy, you run a node and it has an RPC function that will give you a block template containing current transactions from the mempool, then you just have to add the coinbase transaction with the address of where you want the reward to go. I recently did this for fun, built a linux box, installed bitcoin core, ckpool and some CPU mining software, it was not hard. it gets about 125Mhash/sec and will be unlikely to mine a block before the heat death of the universe, but if it does, it will all be mine!

aminok

Ethereum Layer 2 activity over the last week: || || |#||Name|Past day TPS|7d Change|Max daily TPS|30D Count|Data source| |1||Base|32.00|-0.40%|36.99on 2024 Apr 08|77.63 M|Blockchain RPC| |2||Degen Chain|20.13|-25.62%|37.12on 2024 Apr 18|53.07 M|Blockchain RPC| |3||Arbitrum One|17.11|-20.58%|58.97on 2023 Dec 16|48.72 M|Blockchain RPC| |4||Ethereum|13.88|+1.77%|22.70on 2024 Jan 14|36.67 M|Blockchain RPC| |5||zkSync Era|12.10|-6.12%|62.07on 2023 Dec 16|32.49 M|Blockchain RPC| |6||OP Mainnet|7.58|-1.40%|11.29on 2024 Mar 27|20.56 M|Blockchain RPC| |7||Arbitrum Nova|6.07|-26.29%|54.90on 2024 Mar 05|25.54 M|Blockchain RPC| |8||Blast|4.87|+2.53%|9.40on 2024 Mar 01|13.54 M|Blockchain RPC| |9||Immutable X|4.87|+151.59%|39.35on 2022 Mar 11|7.34 M|Closed API| |10||Linea|4.60|-9.14%|55.70on 2024 Mar 31|45.29 M|Blockchain RPC| |11||Mantle|2.83|-1.95%|25.47on 2023 Dec 27|7.65 M|Blockchain RPC| |12||Scroll|2.56|-36.96%|6.29on 2024 Feb 25|10.16 M|Blockchain RPC| |13||Zora|2.26|-67.39%|12.81on 2024 Apr 09|14.25 M|Blockchain RPC| |14||Mode Network|2.19|+6.11%|2.82on 2024 Apr 08|4.82 M|Blockchain RPC| |15||ApeX|1.82|-5.48%|3.24on 2024 Feb 22|4.99 M|Closed API| |16||Apex|1.70|+20.13%|1.75on 2024 Apr 22|3.23 M|Blockchain RPC| |17||dYdX v3|0.93|-37.99%|11.45on 2022 Feb 15|3.27 M|Closed API| |18||Sorare|0.83|-3.98%|2.31on 2022 Oct 23|1.47 M|Closed API| |19||Manta Pacific|0.81|+35.18%|5.88on 2023 Dec 22|1.82 M|Blockchain RPC| |20||tanX|0.73|+20.00%|1.22on 2024 Feb 18|1.64 M|Closed API| source: [https://l2beat.com/scaling/activity](https://l2beat.com/scaling/activity)

KoreanJesusFTW

> It's funny though that Ethereum infrastructure is run substantially by Infura, which is majority owned by JP Morgan, while Cardano infrastructure is run by a decentralised community. If you know how Ethereun is structured, you know that this is simply not true. Infura is just an RPC endpoint. Matter of fact, I can mount my wallet in Metamask and make it use one of my nodes as the RPC endpoint instead of Infura. The entire Ethereum network is run by stakers - primarily by solo stakers, individuals that bootstrapped the beacon chain when it switched from POW to POS. In contrast, ADA runs a DPOS variant because they didnt have as much research as Ethereum did. All Proof Of Stake that existed prior to ETH POS are done this way - DELEGATED POS (that's what the D stands for). It centralizes on the delegates much like the pools in mining. Sure, Ethereum now has custodial staking providers. This is primarily for participants that's got less that 32 ETH to stake. > Also Ethereum devs have openly declared that governance by the Ethereum community is impossible, Citation required. One would suspect that this is merely the opinions of a few. Governance is there, decisions are being made by the community on each EIP that goes through. It works and it exists. We see this on the daily. This is one of the reasons why everything on top of Ethereum works. It is also clearly the home of DeFi. The chain has no special "shutdown feature" once in a while because it is designed very well. World's best minds are working in Ethereum. > while in Cardano community governance is readying to launch. This is comparing something that exists and clearly working to something that's not even there... Yeah, let that sink in for a while. > It's almost like if you look at facts rather than narratives, your whole point is turned upside down. Sure, that's why ADA strive so hard to be that ETH killers that many pose as for years and I suspect will continue to do so for years to come, right?. Let's face it in a competition, you keep your eye on the one that's ahead. Not the ones that ate the dust behind you. ADA clearly had it's eyes on ETH for since it launched. That forced implementation of smart contracts even though smart contracts does not natively work with UTXO (Charles chosen addressing scheme for ADA --- wow!). This is BTW, the reason why EUTXO was created. That's a point per point rebuttal. I welcome any counter argument with the relevant proof.

jawni

Not all, but many: The exchanges you use, VC funded. The wallets you use, VC funded. The RPC services your wallet connects to, VC funded. The validator software taking your transaction, VC funded. The block explorer you use to check the transaction, VC funded. The payment processors working on accepting crypto, VC funded. Even *this website*, VC funded.

cosmic_censor

In some cases, you can monetize your RPC node using POKT. I am not sure how profitable it is considering the hardware requirements of an RPC node but it does make some profit.

Michael__X

This is a bad idea but that's not what you asked. I'm not too sure about sol but on EVM chains you need a RPC provider and a basic understanding of the contracts you're trying to interact with e.g uniswap. https://www.quicknode.com/guides/ethereum-development/smart-contracts/how-to-interact-with-smart-contracts The exchange route is probably the easiest tbh but you can't trade all the shitcoins. Jusst read their api docs

croissant_auxamandes

Not everytime; just use MEV protection RPC, or Cowswap and such. As far as I know, I don't even think there's MEV on Solana.

ConfidentialX

Also partnered with XDC Network for RPC.

KronosTP

The chain isn’t made to let some people have better luck with transactions or not. First off, do you know how an RPC works, before talking about their pricing?

KronosTP

Bro you sound very badly informed of Solana for a developer, no offense. There is no “higher priority by choice” although maybe you are using a shit RPC. (Use Helius). Priority fee markets are not ideal on Solana, spamming through a 1SOL transaction is more your problem than it is Solana’s, that’s like paying a 100000 dollar fee on ethereum and calling eth garbage.

JeopardyQBot

ah okay, i've never used that wallet but it seems like they support custom RPC settings which well let you connect to nova. there's an imtoken support page about it. so you just need to figure out where to add a custom RPC. then you can get the settings from DefiLlama's Chainlist site for arbitrum nova and put them in. the specific rpc url that you use doesn't matter so much, there are usually a few options, can try a different one in the list if your having trouble with transactions sending these settings should work but in general get them from Chainlist ChainID: 42170 Currency: ETH RPC: https://arbitrum-nova-rpc.publicnode.com Block Explorer: https://nova.arbiscan.io/

aminok

Ethereum Layer 2 activity over the last week: || || |#||Name|Past day TPS|7d Change|Max daily TPS|30D Count|Data source| |1||Linea|53.28|+147.72%|55.70on 2024 Mar 31|46.68 M|Blockchain RPC| |2||Base|26.68|+53.80%|27.13on 2024 Mar 30|35.60 M|Blockchain RPC| |3||Arbitrum One|14.84|-14.59%|58.97on 2023 Dec 16|35.73 M|Blockchain RPC| |4||Ethereum|14.42|-2.62%|22.70on 2024 Jan 14|37.98 M|Blockchain RPC| |5||zkSync Era|11.73|-20.97%|62.07on 2023 Dec 16|34.18 M|Blockchain RPC| |6||Arbitrum Nova|9.67|-75.16%|54.90on 2024 Mar 05|97.25 M|Blockchain RPC| |7||OP Mainnet|6.95|-11.01%|11.29on 2024 Mar 27|17.25 M|Blockchain RPC| |8||Blast|4.57|-4.54%|9.40on 2024 Mar 01|9.70 M|Blockchain RPC| |9||Scroll|3.94|-31.11%|6.29on 2024 Feb 25|9.91 M|Blockchain RPC| |10||Mantle|2.69|-14.22%|25.47on 2023 Dec 27|6.83 M|Blockchain RPC| |11||Immutable X|2.50|+21.98%|39.35on 2022 Mar 11|7.43 M|Closed API| |12||Zora|1.84|+38.51%|1.89on 2024 Mar 31|2.83 M|Blockchain RPC| |13||ApeX|1.76|-13.84%|3.24on 2024 Feb 22|5.26 M|Closed API| |14||dYdX v3|1.44|+14.32%|11.45on 2022 Feb 15|4.75 M|Closed API| |15||Mode Network|1.24|-28.45%|2.21on 2024 Feb 05|3.08 M|Blockchain RPC| |16||Starknet|0.74|-49.38%|12.30on 2024 Feb 20|4.89 M|Blockchain RPC| |17||Metis|0.69|-4.15%|9.37on 2024 Jan 19|1.62 M|Blockchain RPC| |18||Manta Pacific|0.60|+1.07%|5.88on 2023 Dec 22|1.66 M|Blockchain RPC| |19||tanX|0.57|-22.22%|1.22on 2024 Feb 18|1.86 M|Closed API| |20||Sorare|0.41|-20.74%|2.31on 2022 Oct 23|1.45 M|Closed API| source: [https://l2beat.com/scaling/activity](https://l2beat.com/scaling/activity)

One_Boot_5662

I cannot imagine any off the shelf application that would do this, because the distinction you are making makes no sense for ordinary users. Signing transactions is signing transactions. You would have to build it yourself. An RPC server with a client on a different machine physically secured away from the server, that only allows creation of transactions with certain criteria.

HSuke

Depends on which aspect. **For validators**: PoS in general is extremely hard and next-to-impossible to compromise for security compared to PoW, so this is mainly for censorship. It used to be during its first year of operations. But then it started pushing hard for 3rd-party validators, and it's been far more decentralized than Ethereum and Bitcoin when measured by the Nakamoto Coefficient. The only popular network more diversified than Solana is Cardano. **For client diversity**: It's more decentralized than most blockchains, but Ethereum is by far the most decentralized in this aspect. **For archive node and RPC requirements**: More centralized than other blockchains due to high hardware requirements.

moonstone4759

Core has no address index, except if you're using Core as a wallet, it knows your own addresses. Those wallet RPC commands are only for your own wallet, not useful for an explorer The Core API is never going to give you any information about arbitrary addresses

xeaxant

You may be looking for [`submitblock`](https://bitcoincore.org/en/doc/26.0.0/rpc/mining/submitblock/) RPC to send your [serialized block](https://developer.bitcoin.org/reference/block_chain.html#serialized-blocks). >`bitcoin-cli submitblock [hex]` >Send a raw block in to the network. >For [example](https://learnmeabitcoin.com/technical/mining/#submitblock), this is the genesis block: >`$ bitcoin-cli submitblock 0100000000000000000000000000000000000000000000000000000000000000000000003ba3edfd7a7b12b27ac72c3e67768f617fc81bc3888a51323a9fb8aa4b1e5e4a29ab5f49ffff001d1dac2b7c0101000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4d04ffff001d0104455468652054696d65732030332f4a616e2f32303039204368616e63656c6c6f72206f6e206272696e6b206f66207365636f6e64206261696c6f757420666f722062616e6b73ffffffff0100f2052a01000000434104678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef38c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5fac00000000` > Note: This is a complete raw block. It must include the block header, the transaction count, and all the raw transaction data. Good luck getting the byte order right.

HSuke

I'm the one who raised the Solana alarms on its transaction failures last week. Despite that, I'm still a Solana user (though I use Ethereum more). I'm a bit of an anomaly because I know blockchain very well. Most users do not care about tech, and only a small portion care about decentralization. Most users only want things to be fast and cheap. Solana fees are cheap on non-congested days (cheaper than Polygon PoS). It's effortless to send transactions fee-wise. Solana is not as fast as it claims, but it's still faster than most blockchains. 1000 TPS is fast enough for most. The transaction failures are bad, but they're mainly degens just trying out every possible combination of swaps until one of them goes through. If you're just sending tokens, they won't likely fail. Realistically, people have a moderately-high tolerance for outages. Traditional systems typically have 99.5% to 99.9% of uptime SLA. It's extremely rare to have higher SLA than that because there are multiple parts that can go wrong: server, network, routing, DNS. Five 9s of uptime ~~~~for a complete system does not exist outside of SCADA and military. Solana is up about 99.9% of the time, which is on the upper-end. If Solana is down for 10 hours, most users are probably not going to notice it unless they're active day traders. According to popular narrative, validator decentralization is bad on Solana. In reality, it's more decentralized (by Nakamoto coefficient) than nearly every blockchain that is not Cardano. It's also the only other network besides Ethereum to attempt client diversification. That's a good thing because current node development for most blockchains is very centralized, and that's something very few people talks about but should be discussed. ------------- On the other hand, Solana is getting worse and slower. They need a better solution for MEV, which has been solved on EVM years ago. Priority fees are causing transactions to get in the $0.01 to $0.10 range. The delayed transactions in the mempool are a huge problem when it gets congested. I'm also worried about Archive Nodes. Solana is a monolithic blockchain and can't segment its network and data like Ethereum + L2s. Normal Solana nodes prune everything and track the minimum state. Solana produces petabytes of data. Only archive nodes store history and full account state, and they're expensive to maintain. It only has 1 decent blockchain explorer: Solscan. The rest are slow, unstable, and provide a horrible UX. It's extremely expensive to run a Solana RPC or Archive node. RPCs are in the $10-25k/yr range. Archive nodes are in the $100k-500k range depending on how much they're tracking and what services they provide. This is going to be hard to scale years from now. There are rumors that Firedancer will fix things, but who knows until it's battle-tested.

aminok

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)

cdbriggs

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!

cdbriggs

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!

cdbriggs

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!

60minutesmoreorless

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/

aminok

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|

Maxx3141

>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.

_TheWolfOfWalmart_

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?

systembreaker

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.

peyoteBonsai

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

Smiling_Jack_

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.

Present_Bill5971

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

VirtualWord2524

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

ThatInternetGuy

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

TheAntagonist202

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.

jawni

This is Helius the RPC provider, not Helium.

Ok-Study3863

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!

TapDancingGhoul

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.

bmanzzs

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?

ske66

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

ske66

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

dandoii

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.

dandoii

> 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.

tvanborm

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

Ok-Study3863

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.

Ok-Study3863

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.

MinimalGravitas

> 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.

MinimalGravitas

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.

tahirjahi

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

OneRobotBoii

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.

iyarsius

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?

HSuke

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.

mcc011ins

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.

mcc011ins

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.

ZodiacManiac

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.

TheAntagonist202

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.

sandworm87

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.

krakrakra

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.

Desperate-Barnacle-4

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)

HSuke

**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.

MinimalGravitas

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

MinimalGravitas

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.

MinimalGravitas

> 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!

2070FUTURENOWWHUURT

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

coinfeeds-bot

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.

wallynext

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.

Sygian

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.

HSuke

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.

Fastrunad

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!

grofexnihilo

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.

therykers

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.

ilushkin

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).

yorickdowne

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

yorickdowne

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.

ilushkin

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.

DBRiMatt

*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

rootpl

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"

rootpl

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?

craigmorris78

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?

odonnellnoel

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.

jonyta

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?

cosmic_censor

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!

aminok

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 | |

Fiach_Dubh

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)

Fiach_Dubh

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.

KOOLBREEZE144

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.

kamarr

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.

MoneroArbo

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

Bitcoin_Maximalist

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).

TertlFace

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.

LilianaMoten

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.

HospitalNovel2635

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.

Black_finz

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.

nagrom0202

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)

influ

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.

clunkyhumanoid

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.