Node Development
Blockchain node software development and customisation — clients, plugins, performance tuning and custom APIs.
- WalletSigns transaction
- Smart contractVault.deposit()
- BlockchainIncluded in block
- IndexerEvent → Postgres
- APIGraphQL · webhooks
- ApplicationBalance updated
#…4812
12 conf.
#…4813
11 conf.
#…4814
10 conf.
#…4815
pending
Decoded events
- Deposit(0x8f2…a91, 500)confirmed
- Transfer(0x1c7…4de → 0x9b0…77f)confirmed
- RoleGranted(PAUSER, multisig)timelock
RPC failover · 3 providers · reorg-safe indexing
Division
Service area
Protocol & Blockchain Infrastructure
Engagement
Project · Team · Managed
Overview
Sometimes off-the-shelf node software is not enough: you need custom RPC methods, tracing capabilities, performance optimisations, plugin systems or new client implementations. We develop and customise blockchain node software, contributing upstream where appropriate, and maintain custom forks responsibly through network upgrades.
Common use cases
- Custom RPC methodsSpecialised APIs for your application.
- Tracing and debuggingEnhanced trace data for analytics.
- Performance tuningFaster sync and query performance.
- New client implementationClient diversity for a network.
Quick answers
Node Development at a glance
The essentials in brief. Every project is scoped individually — ask us for specifics.
- What is node development?
- Blockchain node software development and customisation — clients, plugins, performance tuning and custom APIs.
- Who is it for?
- Typically Web3 startups, fintechs adding digital assets, and institutions exploring tokenization, stablecoins or on-chain settlement.
- What does Shivacha provide?
- Client customisation
- Plugin development
- Performance optimisation
- Upgrade maintenance
- Testing
- Upstream contribution
- Which technologies are used?
- Ethereum, Arbitrum, Optimism, Solana, Rust, Go (Golang) — chosen to fit your stack and constraints.
- How does the process work?
- Requirements → Design & specification → Implementation → Testnets → Mainnet operations.
- What affects the cost?
- Contract complexity and number of chains
- Custody and wallet model
- Independent audit scope
- Indexing, analytics and back-office tooling
- Compliance integrations (KYC, AML, Travel Rule)
- Upgradeability and governance requirements
- How long does it take?
- A focused contract system or dApp MVP typically takes 8–14 weeks plus independent audit time; institutional platforms usually take 4–9 months.
- How do I get started?
- Share a short brief in the form below, book a 30-minute call or message us on WhatsApp. A senior engineer replies within one business day; NDA on request.
Capabilities
What we deliver
Client customisation
Features added to existing clients.
Plugin development
Extensions using client plugin systems.
Performance optimisation
Storage, caching and networking.
Upgrade maintenance
Tracking network upgrades.
Testing
Consensus and compatibility testing.
Upstream contribution
Contributing improvements back.
Architecture
Engineered right from day one
The layers we typically design for protocol & blockchain infrastructure, adapted to your stack and partners.
- Framework vs customEstablished rollup and appchain frameworks where possible; custom only where justified.
- Bridge riskBridges are high-value targets; designs minimise trust and include rate limits and pause controls.
- Operational resilienceRedundant infrastructure, key management and incident runbooks.
- Upgrade governanceClear, transparent upgrade paths with timelocks.
Delivery
How an engagement runs
- 1
Requirements
Throughput, latency, finality, decentralisation and cost targets.
- 2
Design & specification
Protocol specification, threat model and economic analysis.
- 3
Implementation
Client, contracts and tooling with extensive testing.
- 4
Testnets
Staged devnets and public testnets with monitoring and chaos testing.
- 5
Mainnet operations
Launch, validator onboarding, monitoring and upgrade processes.
Security
Security built into delivery
Controls we apply by default on this kind of work — not a separate phase at the end.
Specification first
Roles, invariants and threat model documented before code.
Adversarial testing
Fuzz, invariant and fork tests plus static analysis on every change.
Key management
Admin keys in multisig or MPC with timelocks on sensitive actions.
Independent audit
Code prepared for — and we recommend — an external audit before mainnet value.
Technology
Tools we use for this
Related services
Often combined with
Blockchain Development
End-to-end blockchain development — architecture, smart contracts, nodes, indexers, wallets and the application layer, built for production.
Learn moreProtocol Development
Blockchain protocol engineering: specification, clients, contracts, testnets and mainnet launch for new protocols.
Learn moreLayer 1 Blockchain Development
Layer 1 blockchain engineering — consensus, execution environments, networking, tokenomics and validator ecosystems.
Learn moreDedicated team
Blockchain Engineering Team
Engineers for protocols, nodes, indexing, custody integration and tokenization platforms.
Work & insights
Related thinking
Tokenized fund units with on-chain eligibility
How we structure a fund tokenization platform where only eligible investors can hold or receive units.
Learn morePolicy-controlled institutional digital asset operations
A reference design for institutions that need every digital asset transaction initiated, approved and signed under explicit policy.
Learn moreEthereum vs Polygon: choosing where to deploy your smart contracts
Ethereum mainnet offers the deepest security and liquidity; Polygon offers lower fees and fast confirmation. The right choice depends on value at risk, users and ecosystem.
Learn moreFAQ
Frequently asked questions
Is maintaining a custom node fork risky?
It adds maintenance burden at every network upgrade. We minimise divergence and contribute upstream where possible.
Which clients do you work with?
Major Ethereum execution and consensus clients, Solana validators and other network clients depending on need.
Should we build an appchain or deploy on an existing network?
Most applications are better served by deploying on an existing Layer 1 or Layer 2. An appchain or rollup makes sense when you need custom execution, dedicated throughput, fee control or specific governance — and can support the operational overhead.
Do you run node infrastructure?
We design, deploy and automate node, RPC and validator infrastructure in your cloud accounts, with monitoring and alerting, and can operate it under a managed services agreement.
Next step
Discuss Your Blockchain Project.
Tell us about your node development requirements — goals, timeline and constraints. We will reply with questions, an approach and next steps.
- Senior engineer reads every enquiry
- Reply within one business day
- NDA on request
Your details are used only to reply to this enquiry.