Olive Branch Network (olivebranch.base.eth)

The Olive Branch Network is proof that blockchains can be designed to do good. @base.base.eth

• 0 replies
• 1 recast
• 8 reactions

What’s next for $OBN? - Improve layout of website/desktop version of the app - Onboard new nonprofits onto the platform I will reach out to at least 3 nonprofits a week. If anyone has any nonprofits they’d like to see on the platform, please send me a DM ☺️

• 0 replies
• 1 recast
• 4 reactions

🎄☃️ Christmas Time is Almost Here! ☃️🎄 We announced in November that we would be doing a Christmas airdrop for anyone who was staking before Thanksgiving Day. 7,777,777 $OBN will be split among every who was staking at the time of the snapshot. Here is the snapshot: https://github.com/jdmaverick369/olive-branch-network/blob/main/obn-project/snapshots/stakers-airdrop-2025-11-27T07-11-29-626Z.json I will start sending this airdrop out individually from our Farcaster wallet. Thank you for supporting the Olive Branch Network and the nonprofits on our platform! 🎅

• 0 replies
• 3 recasts
• 10 reactions

Why I built $OBN. We need a blockchain/app that helps those who really need it. Whether it’s people, animals, or the environment - the user gets to choose. When a user logs into the OBN app, they see a list of verifiable nonprofits that they are able to stake their $OBN to. Whenever the user claims their pending rewards a portion is redirected to the selected nonprofit. Check it out at: https://dapp.olivebranch.network

• 9 replies
• 22 recasts
• 33 reactions

Here is the latest analytics from our Dune Dashboard. It shows the number of people staking, TVL, and more 🙂 The base layer of the protocol is working as intended. A growing number of people are earning while supporting a nonprofit of their choice on our platform. Thank you to everyone that's using our platform to Stake, Earn, and Give Back ❤️ 🫶 🙏 We are just getting stared!

• 0 replies
• 9 recasts
• 10 reactions

1,000,000,000 $OBN tokens were minted on launch. 💦 40% to liquidity 🪂 30% to airdrop/bug bounty 🎁 10% to charity fund 🌱 10% to treasury 👫 10% to team vesting contract 💦 All the liquidity has been paired to ETH in a Uniswap pool. 🪂 Approximately 50% of the airdrop/bug bounty wallet has been distributed. 7,777,777 $OBN is left in the Farcaster airdrop wallet & 150,000,000 $OBN sitting in the original airdrop/bug bounty wallet. 🪂 The remaining tokens in the Farcaster wallet will be airdropped. For now, the 150,000,00 $OBN will be reserved for possible future learn/earn programs with CEXs and ongoing bug bounties. 🎁 The charity funds only purpose is to bootstrap permalock 1,000,000 $OBN tokens to each nonprofit. This is permanently staked to the nonprofits pool and acts as if it were being staked from their own wallet. So far, 10 nonprofits have been onboarded and bootstrapped. Tokens that the charity fund holds and disperses will never touch the circulating supply. They will all, at some point, start earning nonprofits $OBN. 🌱 As for the treasury funds, they will be used for two things: (1) for partnerships with those that can help push $OBN in the right direction, and (2) for burning - to curve inflation. 👫 The team’s vesting contact has a 4-month cliff, in which no tokens are dispersed. Afterwards, 5% is unlocked every month. After 2 years, all of the team’s tokens will be released.

• 1 reply
• 8 recasts
• 13 reactions

🔄 Update - Pushing StakingPools v9.0 Instead of v8.9.0 (11/11/2025 11:00PM CST) I built OBN StakingPools v8.9.0 with several improvements. During security review before mainnet deployment, I discovered a critical honeypot risk in the `forceExitUser()` function. Instead of deploying the vulnerable v8.9.0, I fixed the issue and created v9.0—which keeps all the good v8.9.0 features, fixes the security flaw, and adds even more improvements. ⚠️ The Problem: v8.9.0 forceExitUser() Honeypot Risk v8.9.0 included a `forceExitUser()` function with a `recipient` parameter: ```solidity function forceExitUser(uint256 pid, address user, address recipient) external { // User's tokens go to recipient address // Admin could call: forceExitUser(pid, user, attacker_address) // Result: User loses all tokens to attacker } ``` This created a **honeypot pattern** - a malicious admin could steal user tokens. Even though the intent was good (emergency exits), the implementation was dangerous. ☑️ The Solution: v9.0 with forceExitUserToSelf() I completely redesigned the emergency exit to eliminate the theft vector: ```solidity function forceExitUserToSelf(uint256 pid, address user, bool claimRewards) external { // User's tokens returned to THEMSELVES ONLY // No recipient parameter = impossible to redirect funds // Admin can trigger it but can't steal tokens } ``` ➕ What v9.0 Includes Carried Forward from v8.9.0 (solid features): - `removePool()` - Safely remove pools with charity wallet fallback - `shutdownPool()` - Block new deposits while allowing exits - Pool lifecycle management architecture Fixed in v9.0 (security improvement): - `forceExitUser()` → `forceExitUserToSelf()` - Emergency exit without theft vector Brand New in v9.0 (enhancements we added): - `migrateBootstrap()` - Nonprofit bootstrap address migration (atomic, safe, preserves rewards) - Reward preservation validation (prevents silent reward loss down to 1 wei) - Lock overflow prevention (prevents lock corruption) - Atomic charity wallet updates (all-or-nothing operations) - Extra hardening validations for edge cases

• 1 reply
• 5 recasts
• 12 reactions