Solana Blockchain for Disaster Aid: Lessons from a Hackathon Project

How we built a decentralized disaster aid tracking ledger on Solana Devnet to guarantee NGO transparency while maintaining beneficiary privacy.

// summary (tldr)

Evaluating the tradeoffs of on-chain auditable ledgers versus private off-chain citizen credentials under active crisis workloads.

The Trust Crisis in Disaster Relief

During major global humanitarian crises, millions of dollars in donations flow into non-governmental organizations (NGOs). However, checking exactly how and where those funds are spent remains a persistent challenge. Logistical overhead, localized leakage, and lack of real-time records can result in delayed relief payouts.

We asked ourselves: Can we use a public blockchain to establish an immutable, public audit trail for relief disbursement?

To test this, we built a decentralized ledger using the Solana blockchain. This post reviews the technical design, Anchor framework implementation, and privacy safeguards we developed.

---

Why Solana?

Many enterprise blockchain projects rely on Ethereum or Private Hyperledger instances. For crisis response, both present major bottlenecks:

Ethereum: Transaction fees (gas) can spike to $10–$50 during network congestion, which would devour a large portion of micro-aid payouts. High block times (12 seconds) are too slow for real-time item collection.

Hyperledger: A private chain loses the primary benefit of public trust—anyone should be able to audit the ledger without requesting permissions.

Solana resolves these friction points:

Sub-second finality (~400ms block times).

Transaction fees that are fractions of a cent (typically $0.00025).

Devnet environments that allow clean SPL token simulations without financial risks.

---

Smart Contract Architecture (Rust & Anchor)

We structured the smart contract state machine in Rust using the Anchor framework. The contract maps accounts representing donors, NGOs, and shelter outposts:

#[program]
pub mod disaster_aid_tracker {
    use super::*;

    pub fn allocate_funds(ctx: Context<AllocateFunds>, amount: u64) -> Result<()> {
        let allocation = &mut ctx.accounts.allocation;
        allocation.amount = amount;
        allocation.timestamp = Clock::get()?.unix_timestamp;
        Ok(())
    }
}

By storing allocation transitions on-chain, anyone can trace the supply path of emergency aid:

`Donor Wallet` $\rightarrow$ `Global NGO Vault` $\rightarrow$ `Local Relief Payout Outpost`.

---

Solving the Privacy Dilemma

The most critical challenge in Web3 civic design is privacy. If you publish a beneficiary's wallet address and payout amount to a public blockchain, you expose their identity, location, and vulnerable state to the entire world.

To solve this, we implemented a hash-linked mapping mechanism:

Beneficiary identities are stored on secure local databases managed by local relief shelters off-chain.

When an outpost issues aid, they generate a SHA-256 hash of the beneficiary's local ID credentials combined with a daily salt token.

The smart contract records the transaction using this one-way hash token.

Public auditors can verify that $N$ distinct, valid tokens were redeemed at a specific shelter outpost without knowing the names or details of the citizens who received them.

---

Conclusion

Building on Solana Devnet proved that low-fee public ledger tracking is viable for humanitarian relief. By keeping personal data off-chain and tracking value flows using immutable hashes, we can achieve absolute transparency without compromising citizen privacy.