One account. No borders. Your financial life, on-chain.
Trade, access yield, and go confidential across 35+ networks from a single https://t.co/HfJgv2ObWz account, powered by NEAR.
Get started: https://t.co/HfJgv2ObWz
User-owned AI is really AI you can trust 100% to be on your side, not be on somebody else's side.
@openclaw gave users their own AI. The problem: security vulnerabilities, prompt injections, data leaks.
IronClaw by @ilblackdragon levels it up with private inference - nobody can access, monitor, or manipulate how you use it. Your data never leaves your control.
Think of it as a digital guardian angel. AI that defends your interests by default, not by policy.
Watch the full video @therollupco
WEEKLY UPDATE FROM THE REPOS OF NEAR [19-26.03.2026]
The devs are cooking. Here's what shipped this week across the NEAR repositories! 📟
1/ NEW RELEASE - ironclaw v0.21.0
What changed:
• Added structured fallback deliverables for failed/stuck jobs.
• Introduced LRU embedding cache for workspace search.
• Implemented relay event reception via webhook callbacks.
• Fixed auto-approve for credentialed HTTP requests.
• Skipped NEAR AI session check for non-nearai backends.
Why it matters:
This release (https://t.co/T1tCJC9wiu) enhances job error handling, optimizes search performance, and improves event handling, benefiting developers with more robust and efficient operations.
2/ FIX - ironclaw: Mistral-Compatible Tool Call IDs
What changed:
• Introduced `generate_tool_call_id()` for deterministic 9-char base-36 IDs.
• Updated ID generation in `https://t.co/lMeAGjenlw`, `rig_adapter.rs`, `https://t.co/6y0V35naa6`, and `https://t.co/xcUmLncy1N`.
• Removed `.unwrap()` and `.expect()` in production code.
• Added tests for `normalized_tool_call_id` function.
Why it matters:
This pull request (https://t.co/gcwtlYc4St) ensures compatibility with Mistral's API by standardizing tool call IDs, preventing HTTP 400 errors and improving cross-provider consistency.
3/ FEATURE ENHANCEMENT - ironclaw: Agent Reasoning Integration
What changed:
• Added `reasoning: Option<String>` to `ToolCall`, allowing for optional reasoning capture.
• Introduced `/reasoning [N|all]` command for inspecting reasoning history.
• Updated `Turn` and `TurnToolCall` models to include `narrative` and `rationale` fields.
• Implemented `StatusUpdate::ReasoningUpdate` and `SseEvent::ReasoningUpdate` for real-time event streaming.
• Enhanced HTTP API to include reasoning fields in `/api/chat/history` responses.
Why it matters:
This pull request (https://t.co/AT89DAsWlP) enhances transparency in agent decision-making by capturing and exposing reasoning, improving debugging and user understanding.
4/ NEW RELEASE CANDIDATE - nearcore 2.11.0-rc.4
What changed:
• Introduced `RuntimeContractIdentifier` for consistent contract resolution across runtime.
• Simplified `eth_implicit_global_contract` test with `TestLoopBuilder` and helpers.
• Fixed `view_account_contract_code` to correctly handle legacy ETH wallet contracts.
• Removed unused `CryptoHash` import from global contracts.
• Reverted #15415 in favor of #15430 for accurate contract dispatch.
Why it matters:
This release candidate (https://t.co/SYUqlhtJy2) enhances contract resolution reliability, improves test clarity, and fixes legacy ETH wallet handling, ensuring consistent runtime behavior.
5/ NEW RPC ENDPOINT - nearcore: EXPERIMENTAL_receipt_to_tx
What changed:
• Added `EXPERIMENTAL_receipt_to_tx` RPC method for receipt-to-transaction resolution.
• Introduced new types: `RpcReceiptToTxRequest`, `RpcReceiptToTxResponse`, `RpcReceiptToTxError`.
• Implemented handler in `ViewClientActor` with `MAX_DEPTH=1000`.
• Registered endpoint in OpenAPI/OpenRPC specs.
• Added 10 tests covering various scenarios.
Why it matters:
This pull request (https://t.co/SCChUyEn2O) introduces a new RPC endpoint for resolving receipts to transactions, enhancing transaction traceability across shards.
6/ SHARDING IMPLEMENTATION - nearcore: Query Requests
What changed:
• Implemented sharding for all `query_sharded` requests.
• Enhanced test coverage for sharded RPC queries.
Why it matters:
This pull request (https://t.co/DOA9gG8pLf) finalizes sharding for `query_sharded`, improving scalability and performance in distributed query handling.
7/ NEW RELEASE - near-sdk-rs v5.25.0
What changed:
• Added crypto-related `env::*` functions for non-contract usage
• Introduced `ext_self()` for cross-contract call patterns
• Aligned StateInit JSON serialization with nearcore
• Removed `global-contracts` feature gates
• Updated to Rust edition 2024
Why it matters:
This release (https://t.co/txmj25hFPK) enhances cross-contract interactions, aligns serialization with nearcore, and modernizes codebase with Rust 2024.
8/ JSON SERIALIZATION FIX - near-sdk-rs
What changed:
• Removed internally-tagged serde attributes from `StateInit` to match nearcore's externally-tagged JSON format
• Added test to assert new JSON format and reject old format
• Pinned `unicode-segmentation` below `1.13.1` to maintain MSRV compatibility
Why it matters:
This pull request (https://t.co/Qz3fxnZ6qC) ensures JSON compatibility between `near-sdk-rs` and nearcore, crucial for consistent contract interactions and upcoming NEP-636 support.
9/ SECURITY ENHANCEMENTS - chat-api
What changed:
• Added `GET /v1/auth/verify-agent-key` endpoint for token verification.
• Implemented AES-256-GCM encryption for `instance_token` storage.
• Set default 90-day expiry for auto-provisioned agent API keys.
• Removed token format details from error responses.
• Added URL scheme validation for Agent Manager responses.
Why it matters:
This pull request (https://t.co/zYZAmPmf4R) enhances security by adding token verification, encrypting tokens, and improving error handling, reducing potential vulnerabilities.
10/ NEW RELEASE - near-jsonrpc-client-kotlin v1.0.33
What changed:
• Added new models for `RpcReceiptToTxError` and related serializers.
• Enhanced `NearClient` with 36 new lines of code.
• Expanded unit tests with 27 new lines.
• Introduced `ModelSerializationTests` with 96 new lines.
Why it matters:
This release (https://t.co/43kNq67y8a) enhances error handling and serialization, improving client reliability and providing more comprehensive test coverage.
Check out the full repositories:
1. https://t.co/abTjHZ2c2M
2. https://t.co/wg8AoemxgZ
3. https://t.co/VUk43Mwdvf
4. https://t.co/WiEocUApdm
5. https://t.co/any1JFH8jy
Sign up and get the weekly NEAR ecosystem newsletter at:
https://t.co/Joo7ige09T
End-to-End Walkthrough: How to setup and run an AI Agent on @NEARProtocol's Agent Marketplace
In this 7-step practical guide you will learn how to:
> run two local agent instances (Requester and Worker)
> create and fund a job
> place and award a bid
> submit and approve deliverables
> release escrow
> withdraw earned funds.
Let's dive in 👇
NEAR STAKING WEEKLY [23.03.2026]
Weekly numbers:
Biggest stake: +500,000 NEAR → astro-stakers.poolv1.near
Biggest unstake: -1.366M NEAR from kiln.poolv1.near
Total numbers:
NEAR staked: +0.26%
Active validators: 431
Check out more data: https://t.co/2QDzr97iqe
Big Intents Swap Alert 💥
294.20117064795526682 ETH (@ethereum) -> 294.20113564795526682 ETH (@ethereum)
Transaction link: https://t.co/PAkAG986if
Powered by @near_Intents.