docs: add reduced transactions and ErgoPay tutorial

[jusungxpark]

Adds a Reduced Transactions / ErgoPay tutorial for milestone 10 of #8, with navigation and a runnable offline example pinned to Fleet SDK 0.12.0 and ergo-lib-wasm-nodejs 0.28.0.

The example performs actual unsigned transaction reduction and a binary round trip, with tests for reduction and ErgoPay transport. Its synthetic chain context is explicitly documented; this is not live wallet, signing, broadcast, or network validation. Static and dynamic ErgoPay handling follows EIP-20, including the recommendation to use dynamic delivery for payloads above 400 characters.

Validation: five tests passed independently in root and reviewer checks; the example ran and printed a 275-byte reduction with base64url output and an offline warning. Staged diff whitespace checks and the VitePress 1.4.3 build passed (root independently verified exit 0). AI-assisted implementation was independently reviewed.

This submission addresses milestone 10 only. The published 150 SigUSD reward remains subject to sponsor confirmation and acceptance; no payment is claimed.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​fleet-sdk/​core@​0.12.0
	ergo-lib-wasm-nodejs@​0.28.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @noble/hashes is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: examples/reduced-transactions/package-lock.json → npm/@fleet-sdk/core@0.12.0 → npm/@noble/hashes@1.8.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@noble/hashes@1.8.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @noble/hashes is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: examples/reduced-transactions/package-lock.json → npm/@fleet-sdk/core@0.12.0 → npm/@noble/hashes@1.8.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@noble/hashes@1.8.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report