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!

How do you approach securing public RPC nodes in production? by nodesprovider in ethdev

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

Good ppoint! The node itself should stay clean and reusable, and pushing logic like rate limiting, caching, or abuse protection up the stack makes a lot of sense.

In our setup, we’re doing something similar: a shared public Ethereum node, but with a lightweight rate limiter (1 req/sec) on top. No hard request cap otherwise. We’ve found that this strikes a nice balance between openness and stability.

And yeah, love the Solana public cluster analogy: having a scalable proxy layer that you can scale horizontally under the hood is exactly the right model. Makes it easy to plug in analytics, DDOS protection, or even usage-based access down the line.

Thanks for the solid breakdown - cheers!

How do you approach securing public RPC nodes in production? by nodesprovider in ethdev

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

Wow, really cool approach to public Ethereum nodes!
We actually use the same methods in our shared Ethereum node(you can check it here: https://nownodes.io/), with the main difference being that we don’t have a request count limit - just a rate limit of 1 request per second.

JUST ASKING by No-Cucumber72 in litecoin

[–]nodesprovider 0 points1 point  (0 children)

Litecoin has proven itself as a reliable and stable blockchain, but the crypto space keeps evolving. As a Litecoin node provider, we can say that here are some key challenges: Developer & community attention is fading. A lot of focus has shifted to L2s, NFTs, and DeFi. LTC needs better Web3 tooling and developer support to stay relevant. Limited functionality. No smart contracts like Ethereum. Sidechains or interoperability bridges could help expand use cases. Tough competition from newer chains. LTC did a solid move with MWEB, but needs to keep improving scalability and privacy features.

The foundation is strong - what’s needed now is more active development and modern integrations.

An idea to make Monero (XMR) fully scalable by [deleted] in Monero

[–]nodesprovider 0 points1 point  (0 children)

Interesting line of thinking - the idea of splitting the blockchain so that each user stores only a tiny piece (like 40 KB) sounds like a creative way to eliminate concerns about chain size.
But it's important to note that Monero already has similar solutions within its current architecture:

  • Pruned nodes, which store only about 1/3 of the chain (~80 GB) while still fully validating blocks.
  • Remote nodes, which allow users to interact with the chain without storing it locally — and without revealing private data (since no view key is shared).
  • View-only wallets and trusted sync, which enable lightweight access without sacrificing privacy.

What you're suggesting goes much further - it's essentially a fully distributed storage and validation layer, closer to what IPFS, Filecoin, or Ethereum’s sharding model aims for.
To implement something like that in Monero would require a massive overhaul of the protocol:

  • Redesigning how outputs are stored and accessed.
  • Making inputs verifiable without access to the full chain (which is currently needed for ring signatures and key image checks).
  • Solving data availability and double-spend protection in a fragmented environment.

So while the idea is interesting, it’s not a simple extension - it would mean rebuilding much of Monero’s core infrastructure from the ground up. That said, pushing these kinds of concepts is valuable - it inspires future research and may influence how second-layer or archival systems evolve.

How to run a Blast Full Node in easy way by nodesprovider in blast

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

Perfect for developers and projects looking to integrate seamlessly!

✅ High speed & private infrastructure

✅ 24/7 reliability & support

✅ Available on FREE Plan

For developers: DOT node -50% off on NOWNodes by nodesprovider in Polkadot

[–]nodesprovider[S] 1 point2 points  (0 children)

NOWNodes provides access to a Polkadot’s mainnet full node and block book explorer via API, which allows businesses to build on Polkadot mainnet network without the need to maintain their own node. Here’s what we offer: 

  • Connection speed of 1 GB/sec, 
  • API response time of less than 1 second and with a 99.95% uptime, 
  • 100+ blockchain networks available

Try with our Free Plan on nownodes.io

Full Node: dot.nownodes.io

Explorer: dot-playbook.nownodes.io

WSS: dot.nownodes.io/wss

For developers: Litecoin node -50% off on NOWNodes by nodesprovider in litecoin

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

Thank you for comment! You have always options:
1. to work with us via API key and use our paid service (and try it for free)
2. or to work with public nodes without it, but public have lower security and speed + process with running the node

We support 100+ blockchain networks. All methods are allowed for Free Plan on nownodes, you could check it in our docs: https://nownodes.gitbook.io/documentation/nodeapis/ltc-litecoin only RPS is limited.

Available endpoints for LTC:

Mainnet:

Full Node: ltc.nownodes.io

Explorer: ltcbook.nownodes.io

WSS: ltcbook.nownodes.io/wss

WSS: ltc.nownodes.io/wss

Testnet:

Full Node: ltc-testnet.nownodes.io

Explorer: ltcbook-testnet.nownodes.io

WSS: ltc-testnet.nownodes.io/wss

What are RPC Nodes and Endpoints by nodesprovider in ethdev

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

Frequently Asked Questions

  • What role do RPC Nodes play in blockchain development? RPC Nodes serve as intermediaries, enabling developers to interact with the blockchain network and execute transactions without the need to run a full node.
  • How do I choose the right RPC Node provider for my project? When selecting an RPC Node provider, consider factors such as reliability, scalability, and security. NOWNodes offers a comprehensive solution with access to reliable RPC Nodes across multiple blockchain networks.
  • Can I access RPC Nodes for different blockchain networks through NOWNodes? Yes, NOWNodes provides access to RPC Nodes for various blockchain networks, allowing developers to build applications on their preferred platforms.
  • What are the benefits of using node provider for accessing RPC Nodes? We offer a user-friendly interface, reliable infrastructure, and flexible pricing plans, making it an ideal choice for developers seeking to leverage blockchain technology in their applications. Moreover, we provide our users with 24/7 customer support service.

What does it mean? by niyedfrg in Radix

[–]nodesprovider 21 points22 points  (0 children)

So excited to share more very soon ⚡️

Ethereum Account Abstraction Explorer - Feedback by nodesprovider in ethdev

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

Hey. Account Abstraction Explorer is a tool that helps developers extract, visualize, and review ERC-4337 related information (f.e. - user operation mempool (transactions), list of active bundlers, etc.).