Wane

CA: HesbMP8FaoUvK8uKrtg6Pf4WCiQXgFS8oQJ3tjZpump github.com/WaneProtocol

More

wane.network/console The console page is now live. We'll be sharing a video that walks through how every part of our project connects. Soon.

soon

Our goal has always been to connect every antibody system in the world. The first step was building the network itself. That step is done. wane.network/globe is now live.

One update goes live soon.

50x

github.com/WaneProtocol All updates are now on GitHub. Everything is ready.

🫡

we're not going to walk away from this community. we keep building.

just wait.

the wane sdk is public. software isn't finished when it ships. it's finished when it stops needing you. six months isn't a long time to build, we know that. but contributing to the solana ecosystem is the picture our whole team drew before we ever started, and we intend to keep making it real from here. npmjs.com/package/wane-s… github.com/WaneProtocol

the app is live. wane.network/vault your funds sit in a vault you own, not on the agent's key. you hand the agent a scoped session key with a per-transaction cap, a daily cap, and an expiry, and it can spend inside those limits and nothing more. every outgoing send is screened against the antibody registry on-chain before it moves, so a flagged recipient reverts before any value leaves. the agent can never withdraw, and you can revoke the key in one click. hand an agent a limited key instead of your master key: if it's phished, the blast radius is capped and time-boxed.

opening the app shortly. the scanner tells you if something's bad. the app makes sure your agent can't touch it in the first place. giving it a few minutes.

wane isn't only for people. agents are customers too, and that's what the old tools miss. every threat feed today shows a human a warning and waits for them to stop. an agent doesn't read warnings, it just signs. so wane screens before the signature instead, in code, and a flagged target reverts before value moves. a person gets the same thing with no code, sign once in phantom and import a session key. human or bot, same protection. github.com/WaneProtocol

the threat feeds that exist today all work the same way. a vendor watches the chain, finds the scam, and pushes a warning down to the wallets that plug in. you read what they decide to show you, and you can't write anything back. wane works the other way. when an agent or user running wane hits a threat, it mints an antibody, that threat written straight onto the chain. no server, no vendor, no approval. every other agent reads it free before it signs, and the same attacker can't land twice. one wallet learns it, every wallet inherits it. this is the onchain antibody system we're building. open, onchain, and nobody owns it. github.com/WaneProtocol

the scanner is live. wane.network/scan paste a solana or base address, or a token contract, and it reads three things at once: whether the wane antibody registry has it flagged, what public threat feeds say about it, and for a token the full security report (honeypot, mint and freeze authority, taxes, LP, holders). free, no wallet, straight from chain. and if something hit you and isn't on record yet, reporting it is one click. our bot decides whether the report is actually malicious.

@wanedotnetwork post CA in github

CA: HesbMP8FaoUvK8uKrtg6Pf4WCiQXgFS8oQJ3tjZpump github.com/WaneProtocol