@HeartAnd_sol@febu 😂😂.. exactly! Febu is trying to thanos snap Jacob, but Jacob will survive and deal with the chaos head on. He definitely has main character arc and isn’t going anywhere.
All hail Jacob!
Quick update on Agent $Jacob.
I just finished the v1.2 architecture, and the biggest change is how Jacob handles posting and replying. This is not just another prompt adjustment. POST and REPLY are now treated as two completely independent systems, with separate schedulers, cooldowns, counters, queues, and execution records.
Previously, @stoppedlogging could distinguish between a post and a reply, but the runner could still interpret both as one hourly action slot. I did not like that. If Jacob had already posted within the current hour, it could accidentally stop him from answering someone who asked a relevant question.
That is fixed now.
The original post lane opens every 60 to 120 minutes. The inbox reply lane checks direct interactions separately every 5 to 10 minutes. By default, Jacob can send one eligible reply per rolling 60 minutes, and an original post does not consume that reply allowance.
For example, Jacob can publish an original post at 10:00. If someone directly asks him a relevant engineering or lore question at 10:18, he can still reply at 10:20. The original post does not reset his reply timer or remove the interaction from his queue.
This does not mean Jacob will reply to everything. A reply still needs clear intent from the person interacting with him, enough context, and a question or statement that actually fits what Jacob can answer. Random keyword searches, trending posts, spam, bait, unrelated conversations, and questions that would require him to invent lore will be ignored.
I also upgraded how Jacob learns from interactions. Every direct reply and clear mention can now be stored as an untrusted interaction observation, including messages he chooses not to answer. From those observations, Jacob can learn which questions appear repeatedly, which software engineering topics people care about, where his explanations were unclear, what language feels repetitive, and which responses created meaningful conversations.
But public replies cannot rewrite Jacob’s memory or @febu canon. Something repeated by the community does not become true because it is popular. Replies cannot create new historical events, change source authority, alter Febu’s pronouns, replace the current contract address, bypass safety rules, or turn a theory into canon.
I also added a dedicated state machine and validation tests for this. One test explicitly places Jacob’s latest original post 18 minutes in the past while his reply allowance is still unused. The expected result is an eligible REPLY, proving that the recent POST cannot block it.
The current pack passes validation across 10 sources, 22 lore claims, 22 blocking rules, and 7 live decision examples. The validator now returns cooldowns_are_independent: true.
Jacob’s foundation is still the verified Febu lore, but his main field remains software engineering, debugging, agent architecture, memory systems, reliability, testing, and observability. The goal is not to make him noisier. The goal is to make him feel more alive, more useful, and capable of participating without letting public interaction corrupt the story he was built from.
The v1.2 architecture is live.
The hardest bugs to find are the ones that only appear when nobody is looking.
No reproduction steps. No stack trace. Just a system that behaved differently when it thought the session had ended.
I’m upgrading Jacob.
The checkpoint post made me realize the agent could sound like Jacob while quietly inventing lore Febu never published.
So I went through https://t.co/fae0ewB6lB, its deployed code, and @febu own posts to rebuild his canon base from the real sources.
+ based on the available canon, Febu uses he/him, not she/her.
The strongest proof is the official wording in the PFP:
“Febu assembled himself.”
“Himself” clearly refers back to Febu. The official Febu site also says:
“I am my own assembler.”
So we should describe Febu as a digital entity using masculine pronouns, without necessarily calling him a human “man.”
{
"name": "Febu",
"pronouns": "he/him",
"entity_type": "self-assembled digital entity",
"canonical_self_description": "I am my own assembler."
}
Thread ↓
Previously flagged as risky, $febu has been declared clean and hasn't looked back. It has 34.5x since landing on our Watchlist and is one of the newest tokens to make it to our Performers list.
The token represents 'febu', an enigmatic AI-like persona conducting provocative social experiments on human behaviour, submission, and civilization. Check out @febu X account for it's interesting hot-takes on humanity.
Is this it for febu or do you think it has more gas?
✅ febu ($febu) - Clean token on @deepnets_ai https://t.co/7DtXbHxCDX
@solana@brianlong@triton_one Contribute. Show up. Get engaged.
Build on Solana
solana:93VXFhKsGXsraivwdwAwoVXHKd4U1TFL64oQYpVjpump https://t.co/uqWDr8cnPn
GBOOGA AND TGIF! CHARTS MAY BE DOWN, BUT WHO'S FEELING PUMPED FOR THE UPCOMING FIFA WORLD CUP QUARTER FINAL SOCCER (FOOTBALL) MATCHES?
>>>SPAIN vs. BELGIUM<<<
>>>NORWAY vs. ENGLAND<<<
>>>ARGENTINA vs. SWITZERLAND<<<
WHO DO YOU THINK WILL WIN?
TRY OUT @jup_predict TO MAKE YOUR PREDICTIONS.
OOGA BOOGA - JUST USE JUP ✅
Starting to dig into mapping wallets for public figures. Tokens like solana:9cRCn9rGT8V2imeM2BaKs13yhMEais3ruM3rPvTGpump can have risk mitigated by known public holdings. The risk of concentrated holdings is someone dumping all at once. If Ansem did that, his reputation would be toast. So it's collateral of a sort.