Repository navigation
docs: show when the near work was built, how it fits together, and what has run on mainnet - #191
Merged
Merged
Conversation
…at has run on mainnet The README's NEAR section now dates the NEAR work from git: the pre-hackathon tag of 17 October, the first NEAR commit on 4 November, and the pull requests by date. It adds four diagrams (how a message becomes a signed transaction, the agent race with Nova's enclave proof, what stands between a message and your money, and an off-ramp from NEAR to a bank), the NEAR partners used, the tracks entered, and the mainnet transactions a real wallet has signed, linked on NearBlocks. "Not done or not proven" says what is still unsigned and what is down upstream. AGENTS.md gives screening agents the same timeline, the newer NEAR files, the shared code changed in the window, and where the mainnet proof is.
✅ Deploy Preview for useintent ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for useintentadapp ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
A GIF under the product description, with the full MP4 linked. It shows a typed request, the agents comparing Rhea and 1Click, Nova's NEAR AI proof note, then a swap on Rhea DEX and a LiNEAR stake. The caption says its amounts are illustrative and points to the real mainnet transactions.
…through A 32-second system architecture video for Intent on NEAR, at the top of "How it fits together": the system map, one request traced from the chat to NEAR mainnet, the ChainVenue and ChainModule interfaces with each NEAR venue's file, the NEAR AI proof as a sequence, the safety checks by name, and the off-ramp as a sequence. The README shows it as a GIF and links the MP4 with sound. The walkthrough MP4 gets a calmer music bed.
…s one image The NEAR AI proof scene now says what it proves in plain terms: Nova's advice comes from NEAR AI's secure hardware, unaltered, or no note is shown. The video has no sound, since it plays in the README. Below it, an image of the same system: the client, API routes, core modules and outside services, with one request traced through them in eight steps.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For the NEAR Hackathon judges, and for the Claude Code and Codex screening that checks the README against the code.
README: NEAR Hackathon section
pre-hackathontag: 17 Oct, no NEAR code.326753f).hackathon-submissiontag.AGENTS.md
nearai-proof.tsin the NEAR-only diff command.Checked
main.hackathon-submissiontag is pushed.