Repository navigation
docs: MPP Charge verified on testnet (15 Oct 2026) - #3
Merged
Merged
Conversation
The README still said the testnet box rejected a valid MPP payment (1 Oct). Re-tested on 15 Oct with nirium@0.16.1: pull and push both settled on Stellar testnet and delivered (b8c4ed56..., 96d43d6f...). Mainnet stays unverified, and the dated history note is kept. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The README said the testnet box rejected a valid MPP Charge payment (1 Oct). That's out of date.
Re-tested on 15 Oct 2026 (UTC) with the published
nirium@0.16.1(initMpp()+mppFetch()) againstnirium-agent.fly.dev/api/v1/mpp/signals:Payment-Receipt, settledb8c4ed56…Payment-Receipt, settled96d43d6f…Three lines change (settlement row, evidence row, MPP paragraph). The dated 2026-10-07 history note stays, with a 2026-10-15 update appended. Mainnet is still described as unverified, with no confirmed mainnet settlement.
The public mirror (
Eras256/Nirium) and the private source get the same 3-line change, so the next sync is a no-op for this file. The same correction for the SDK README is nirium-protocol/nirium#141.Disclosure: drafted with AI assistance under my direction and reviewed by hand.
🤖 Generated with Claude Code