Sabitlenmiş Tweet
Capy
2.2K posts

Capy
@funofcapy
A description will appear here someday
Capyland Katılım Ağustos 2023
2.8K Takip Edilen793 Takipçiler
Capy retweetledi

I bought a second $ucat. Now they can mate and reproduce
It’s inspiring — I can give life
Enjoy ponzi
@UnicatsETH

Capy@funofcapy
gmeow @UnicatsETH $ucat
English

Added another 25 ethereum:0xd4e43c86334940a246daae8908c9b3cfb97c6817 now 125 in total. This project has more technology and artistry than just ethereum:0x44b28991b167582f18ba0259e0173176ca125505
Believe in something
@unicorev4

Capy@funofcapy
Gm ethereum:0xd4e43c86334940a246daae8908c9b3cfb97c6817 99
English

$UNICORE token ownership renouncement: complete and verifiable on chain
The team has permanently given up admin control of the UnicoreToken contract. The owner of 0xd4e43c86334940a246daae8908c9b3cfb97c6817 now points at a small burner contract whose source code contains a single public function.
Why a burner contract was needed
UnicoreToken uses a two step ownership transfer pattern (the safer kind that prevents typo bricking). The current owner proposes a successor, and only that successor can finalize by calling acceptOwner. Sending ownership to a dead wallet like 0x000...dEaD therefore does not work: the dead address has no private key to call acceptOwner, so the transfer never finalizes and the original owner remains in charge in practice. We needed a real contract to be on the receiving end.
We wrote a minimal contract called UnicoreOwnershipBurner. Its complete public surface is a single acceptOwner function. There is no transferOwner, no setter, no upgrade path, no fallback, no receive function, no rescue method. Once it becomes the owner of the token, the burner has no path to ever call any privileged function on the token. The administrative side of the contract is mathematically dead.
Transactions
Burner contract deploy:
etherscan.io/tx/0xb838e4385…
Propose burner as new owner of the token:
etherscan.io/tx/0xf2b0e4b60…
Finalize transfer (irreversible):
etherscan.io/tx/0xa8c7b065d…
Burner contract on Etherscan, verified source:
etherscan.io/address/0x4613…
Verification in thirty seconds
Open the token's read tab:
#readContract" target="_blank" rel="nofollow noopener">etherscan.io/address/0xd4e4…
1. Read owner(). Returns 0x4613bde1d5FB42CCF8a010bce05Cd15a67bE4503 (the burner, not the team).
2. Open the burner address on Etherscan and switch to the Contract tab. The verified source is roughly 50 lines including comments. Confirm there is no setter, no admin function, no upgrade path.
3. Read burner.renounced(). Returns true.
4. Read burner.renouncedAtBlock(). Returns 25021755, the block where the renouncement finalized.
English

$UCORE Ownership Renouncement Underway
We're in the process of permanently renouncing ownership of both core
UNICORE contracts:
• UnicoreToken — 0xd4e43c86334940a246daae8908c9b3cfb97c6817
• UnicoreHook — 0x80a26a3650d03b6332f0d88450D5c396a2C880Cc
⏱ Why this is taking a few hours
UNICORE was deployed with a TWO-STEP ownership transfer pattern
(transferOwner → acceptOwner). This is the safer pattern that prevents typo-bricking, but it means we cannot simply send ownership to 0xdead, that address has no private key to call acceptOwner, so the transfer would never finalize and we'd technically still be the owner (which defeats the entire purpose).
The correct approach is to deploy a small dedicated "burner" contract whose only public function is acceptOwner(), with no setter, no upgrade path, no fallback, no rescue function // nothing. Once that
burner becomes the owner of our contracts, there is no path on chain for the admin surface to ever be exercised again.
We're writing, testing, and verifying that burner now. We're taking our time on purpose. We're not going to break the protocol just to ship faster, every reward in flight, every active slot, every pool position has to keep working flawlessly during and after this.
🔍 What you'll be able to verify on Etherscan once we're done
1. token.owner() → returns the burner contract address (not our wallet)
2. hook.owner() → returns the burner contract address (not our wallet)
3. Burner contract source on Etherscan → ~50 lines, ONE function, no admin surface whatsoever. The compiled bytecode hash matches the verified source.
4. burner.renounced() → true (with a block-number timestamp showing exactly when the transfer landed)
5. Try to call any privileged function from our deployer wallet // transaction reverts with Unauthorized
Anyone can do these checks in 30 seconds. No trust required.
✅ What keeps working forever after renouncement
Everything user-facing is permissionless by design and unaffected:
• Swaps on Uniswap v4 (3% hook tax fires automatically)
• hook.normalize() — anyone can push accumulated tax to the reward pool
• token.withdrawRewards() — every holder claims their own ETH
• Slot transfers, marketplace listings, swap-based slot mints, all of it
❌ What we permanently give up
• setMaxWallet — the per-wallet cap is locked at its current value
• setAssetBaseURI — the IPFS gateway URL is frozen (we've pinned the artwork redundantly in advance to ensure long-term durability)
• transferOwner — ownership cannot be moved anywhere else, ever
These are the costs we're accepting to give the community the
strongest possible non-rug guarantee.
📡 Updates
We'll post here the moment the deploy lands, with:
- Burner contract addresses + Etherscan verification links
- transferOwner / acceptOwner transaction hashes
- A step-by-step verification guide
— UNICORE team
English

Now I just hold $FIRE
Every buy feeds me
Every sell makes me richer
Every second I do nothing — I earn more
4% tax flowing straight to holders
Multiplier grows the longer I stay lazy
This isn’t a token. It’s a lifestyle
Retiring early wasn’t a dream
It was just one buy away
I won $100 in the daily lottery today
Doing nothing
@fire_earn

English

i think @unicorev4 dev isn't indian gay nigger
ethereum:0xd4e43c86334940a246daae8908c9b3cfb97c6817
Capy@funofcapy
Gm Some @unicorev4 $ucore
English

@Unicurvefun @Openpeg @opensea @uniaudio_fun audio ethereum:0x44b28991b167582f18ba0259e0173176ca125505
and also x.com/funofcapy/stat…
Deutsch

Everything coming to @Openpeg
There will be the @opensea moment for UniCurve
Drop the collections you want to get listed on marketplace.
We will be reviewing each request
NFT2.0 season just started
$uPeg $ppeg $unicurve
OpenPeg@Openpeg
On high demand of this strong loud community $PEPI @pepinscriptions is now listed on marketplace. trade here👇 openpeg.io/c/0x3103cd1602…
English









