Debian Codegraph @

external/feather-docs/content/_guides/formatted_tx_proofs.md

raw
1 ---
2 title: Formatted transaction proofs
3 nav_title: Formatted transaction proofs
4 category: faq
5 ---
6
7 Formatted transaction proofs is a PGP-like message format used to conveniently share Monero transaction proofs without having to copy multiple fields.
8
9 Here is an example:
10
11 ```
12 -----BEGIN OUTPROOF-----
13 Network: Monero Mainnet
14 Txid: 46d9f3eaf8d25b6a5d0847ad0beaece8b153d1b8c25ce317934ec17223025806
15 Address: 463o7kTG4n2AEHNhhV91BK7kZsKd4vRh78xt6LM7Px7o3cp5eZgyuyLHVAWeEkfLcoC78WMZuJ3xZ1SiM4RhbciCB8b8pGS
16
17 A small donation.
18 -----BEGIN OUTPROOF SIGNATURE-----
19
20 OutProofV2SWYVZHfqBwYGNYxDRZryBdXomxA9hS3VLWiRiQZ9YNutAGoq1QxB7j
21 AYwRrhoxJBQ8jj7XCNNfvSwgQaVFjWY5EQHJRW3LgPtV3UmefmQ2wFJPh2iTaCH8
22 zETWpxTrf2RiVY
23 -----END OUTPROOF SIGNATURE-----
24 ```
25
26 To learn how to verify formatted transaction proofs in Feather, see: [Verify transaction proof](verify-tx-proof).
27
28 ---
29
30 ### For developers:
31
32 Formatted transaction proofs can be parsed using this regular expression:
33
34 (Newlines added for readability)
35
36 ```
37 -----BEGIN (?<type>\w+)-----\n
38 Network: (?<coin>\w+) (?<network>\w+)\n
39 Txid: (?<txid>[0-9a-f]{64})\n
40 (Address: (?<address>\w+)\n)?
41 \n?
42 (?<message>.*?)\n
43 -----BEGIN \1 SIGNATURE-----\n
44 \n?
45 (?<signature>.*?)\n
46 -----END \1 SIGNATURE-----
47 ```
48
49 Where:
50
51 - `type` is one of [`SpendProof`, `OutProof`, `InProof`]
52 - `coin` is `Monero`
53 - `network` is one of [`Mainnet`, `Stagenet`, `Testnet`]
54 - `txid` is a 64 character hexstring
55 - `address` is a valid Monero address for the given `network`.
56 - MUST be present if `type` is `OutProof` or `InProof`.
57 - MUST NOT be present if `type` is `SpendProof`.
58 - `message` is an optional arbitrary length message that may contain newlines
59 - `signature` is the proof signature
60 - SHOULD be split into chunks of 64 characters over multiple lines