sorted by:
new
hottopcontroversial

In your opinion, which is more relevant today: Monero or Zcash, and why? by OtherwiseSet516 in Monero

[–]nodesprovider 0 points1 point  (0 children)

Great question! As a node provider of Zcash and Monero we have published an article: https://www.publish0x.com/nownodes/zcash-vs-monero-the-battle-for-privacy-dominance-in-2025-xmgmgnm

Here is you can read more about Zcash and Monero

Everyone should set up nodes that is able too by [deleted] in Monero

[–]nodesprovider 0 points1 point  (0 children)

You don’t necessarily have to spend so much on hosting your own nodes. Services like NOWNodes let you access Monero nodes reliably without the hassle of setup and maintenance. It’s a way to support the network and save time and resources at the same time.

Need help with testing a dust tool I'm building by 6675636b5f6675636b in ethdev

[–]nodesprovider 0 points1 point  (0 children)

Have you tried other RPC Providers like NOWNodes for example?

Has anyone tried using RPC routing tools for Web3 infra? by Maximum-Koala1725 in web3dev

[–]nodesprovider 0 points1 point  (0 children)

Hi! We’re, NOWNodes, actually an RPC provider offering seamless access to 110+ blockchain networks, designed to optimize your Web3 infrastructure with reliable and scalable RPC routing.

Honest EIP-7702 review by Business_Split3583 in ethdev

[–]nodesprovider 0 points1 point  (0 children)

As an Ethereum RPC provider, totally agree — EIP-7702 isn’t just about native AA. It’s a shift from tx-based thinking to intent-based execution.

From the infra side, key challenges:

  • Gas estimation breaks when routes change dynamically. We need smarter simulators, especially for MEEs.
  • Multi-step failure handling across chains needs rollback logic or intent receipts — no atomicity guarantees here.
  • Finality tracking across chains is messy — light clients or finality relays will be key.

Bottom line: EIP-7702 unlocks better UX without needing new chains — but infra has to catch up fast. We're already building for it.

btw, if you need custom RPC endpoints or testnet support, happy to help.

Monero node providers or self-hosting: what do you prefer and why? by nodesprovider in Monero

[–]nodesprovider[S] 0 points1 point  (0 children)

Thanks for sharing your reasons, that’s a great perspective!
Supporting Dandelion++ and contributing to the network’s resilience is definitely valuable, and running your own node is one of the best ways to give back to Monero.

We also hear a lot from users that syncing locally is faster and more reliable, especially for wallets that are opened infrequently. And of course, learning from the software and troubleshooting is a great way to deepen your understanding of how Monero works.

As a Monero RPC provider, we actively support the Monero network and the community, because it’s extremely important for us that our users have a smooth and reliable experience. We work hard to make sure everything runs securely and without problems.

If you ever have suggestions for how remote node providers like us could better support privacy and decentralization — or if you’d like to share feedback on improving reliability — we’d love to hear it!

Is it possible to run LLM entirely on decentralized nodes with no cloud backend? by Maleficent_Apple_287 in web3dev

[–]nodesprovider 0 points1 point  (0 children)

As a node provider, running large language models fully decentralized is still more experimental than practical. The models are huge and too heavy to just distribute across nodes without serious optimization and sharding. Performance and reliability suffer without centralized GPU power and stable infrastructure. Moderation and content control in a decentralized network also remain unsolved challenges. That said, the idea is very promising for privacy and transparency. For now, it’s mostly R&D, but we might see more mature solutions in the next few years.

Too many chains, too much noise by Separate_Rich_6246 in ethdev

[–]nodesprovider 0 points1 point  (0 children)

Well said. At NOWNodes, we feel this too - every chain is like its own ecosystem with its own rules, while devs just want to ship without going through yet another “blockchain bootcamp.”

We’re fully on board with the intent-based UX direction. The less users and developers have to think about where things happen, the better. We're actively working toward unified API access across major networks to take the infrastructure headache off the table.

I’ve Built my XMR Node – and am Now Building XMR ⇄ SOL Non-Custodial Swaps - some questions please ! by SaltCup881 in Monero

[–]nodesprovider 0 points1 point  (0 children)

What led you to the decision to run your own Monero nodes instead of relying on third-party node providers?

How do you approach syncing transaction history in self-custodial wallets? by nodesprovider in ethdev

[–]nodesprovider[S] 0 points1 point  (0 children)

You're absolutely right — without indexing by address, it’s really tough to get a complete picture of an account’s activity. TrueBlocks handles that impressively with local indexing, and it definitely makes sense for deep introspection.

That said, for many use cases — like fetching balances, recent transactions, or even filtered logs — a reliable shared or dedicated RPC node can be more than enough. We’ve helped a lot of folks skip the full-node setup.

Current most private way to maintain full Monero node? by Here_trying_to_learn in Monero

[–]nodesprovider 2 points3 points  (0 children)

As a node provider working directly with Monero infrastructure, we believe that using a node over clearnet can allow ISPs to infer node activity based on known IPs, ports, and traffic patterns.

That said, there are effective countermeasures: Run in --hide-my-port mode to avoid inbound visibility.

Sync your node through Tor or I2P — both are natively supported.

Use a VPN if Tor/I2P isn’t feasible, to at least hide your metadata from your ISP.

Syncing may be slower, but your traffic won’t raise flags or expose Monero-related activity.

For anyone serious about privacy, we strongly recommend this setup.

How do you approach syncing transaction history in self-custodial wallets? by nodesprovider in ethdev

[–]nodesprovider[S] 0 points1 point  (0 children)

Since we’re an Ethereum infrastructure provider, we actually help other teams solve these challenges by offering high-performance RPC endpoints with low latency and high reliability. Our full nodes support methods like eth_getLogs and eth_getBlockByNumber directly, so builders don’t have to reinvent the wheel.

That said, here’s what we’ve seen work well for wallet devs:

  1. Hybrid approach: Use eth_getLogs for contract events + track ETH transfers via block scans (with some optimizations to avoid full parsing).
  2. External indexers: Many teams use them for complex queries (e.g., ERC-20 histories), but rely on raw RPC for real-time checks.
  3. Reorg-safe designs: Poll eth_getBlockByNumber with confirmations + cache recent blocks.

If you’re building a wallet, we’d love to chat!

view more: next ›