Heima (@heimaNetwork) / X

Heima

2,706 posts

Heima

@heimaNetwork

Litentry is rebranding to Heima, shifting our focus from identity aggregation to chain abstraction. Swap+Bridge portal👉linktr.ee/Heima_Network

Joined May 2020

Pinned
Heima
@heimaNetwork
May 25
The Heima team is considering an on-chain governance proposal to burn 16.5M HEI from the Ecosystem allocation, including 12.05M locked HEI and 4.45M unlocked but untouched HEI token. This Ecosystem fund was originally reserved for Polkadot parachain auctions. However, as
22K
Heima
@heimaNetwork
14h
AgentKeys cap minting now carries a K10 proof-of-possession.🛡️ That means the worker now verifies a request-bound client signature from the agent-held device key, rather than relying solely on the broker signature. The broker can still coordinate the request, but the worker no
5K
Heima
@heimaNetwork
Jun 9
⚙️ AgentKeys had a heavy building week last week. • Config storage moved into its own protected class, giving onboarding and memory taxonomy a durable home separate from user memory and credentials. • Broker and worker calls now run through one shared client. Less duplicated
6.3K
Heima
@heimaNetwork
Jun 8
AgentKeys desktop onboarding is now a working ceremony. 🚀 • Email link, no registration form. • WASM daemon bootstraps trust. • Touch ID passkey derives the local wallet. • Master device registers and audits on Heima . • Parent-control panel follows. Security-first AI
00:00
7.2K
Heima
@heimaNetwork
Jun 6
The proposal has passed community governance. The burn does not happen immediately after the referendum concludes. It is scheduled to execute 288,000 blocks after the referendum has passed. Depending on block times, this is expected to be approximately 40–60 days from today.
Heima
@heimaNetwork
May 30
Community voting for the 16.5M HEI burn proposal is now live. The Foundation has voted in favor of the proposal, but the final decision belongs to the community. We encourage everyone to review the proposal, form their own opinion, and participate in the voting process.
14K
Heima
@heimaNetwork
Jun 4
Just a reminder that there is now only 1 day left to vote on the 16.5M HEI burn proposal. If you haven’t voted yet, please take a moment to review the proposal and make your voice heard. The final decision belongs to the community. Thank you to everyone who has participated in
Heima
@heimaNetwork
May 30
Community voting for the 16.5M HEI burn proposal is now live. The Foundation has voted in favor of the proposal, but the final decision belongs to the community. We encourage everyone to review the proposal, form their own opinion, and participate in the voting process.
11K
Heima
@heimaNetwork
Jun 4
A lot of AgentKeys work lately has been around memory.🧠 As agents accumulate more context, history, and workflow state, finding the right memory while maintaining access control becomes increasingly important. AgentKeys is being built as the gate around agent memory. Retrieval
8K
Heima
@heimaNetwork
Jun 4
HEI Cross-Chain Bridge Update 💡 Following Binance’s recent update regarding $HEI deposits and withdrawals on BNB Chain(BSC), we want to remind $HEI holders that the official Heima Token Bridge is available for transferring $HEI from BSC to the Heima Network. For users who
9.3K
Heima
@heimaNetwork
Jun 3
One of the core designs behind AgentKeys is isolation. Not because we expect every agent to become compromised, but because eventually, one of them will. If you’re running ten agents and one gets compromised, that compromise shouldn’t spread to the other nine. 🚧Isolation is
7.3K
Heima
@heimaNetwork
Jun 1
A few small but important AgentKeys updates from last week. 1. Safer agent pairing 🤖 Agents now get their own device key inside their own environment. The master approves the pairing, but the agent never touches the master key. 2. A clearer memory boundary 🧠 AgentKeys owns
8.3K
Heima
@heimaNetwork
May 30
Community voting for the 16.5M HEI burn proposal is now live. The Foundation has voted in favor of the proposal, but the final decision belongs to the community. We encourage everyone to review the proposal, form their own opinion, and participate in the voting process.
26K
Heima
@heimaNetwork
May 29
A lot of what Heima does lives underneath the surface. It's always rewarding to see that work start turning into actual products and experiences people can interact with. Excited for what's coming next 🚀
Wildmeta
@wildmetaHQ
May 28
Alongside prediction markets, we’ve also been redesigning the broader app experience from the ground up, including a new landing page. A lot of work has gone into making the next version feel more polished and cohesive across the entire product experience. Can’t wait for
8.8K
Heima
@heimaNetwork
May 27
As part of the governance process, the Heima team has officially submitted the onchain proposal to burn 16.5M HEI from the ecosystem allocation. The proposal has now passed council voting and will move into the community voting phase in 2 days. Proposal details:
9.8K