I Have Proof of Delivery

2-Scan Protocol • Receiver Confirms • XP Posts

If you received a package or completed a delivery, this is where truth gets recorded. Scan #2 (receiver acceptance) finalizes the event in the ledger as XP.

Enter the delivery credential Type or paste the voucher / delivery credential ID from the package or label.

Confirm final destination Was this the last stop? If yes, settlement can be finalized and recognition can be issued.

Receiver accepts (Scan #2) This is the anti-fraud moment. No acceptance = no finalized entry.

Recognition: When a delivery is confirmed at the final destination, the system can mint a New World Penny service award to the final delivery person (and optionally record in-route “handoff” touches).

What is the New World Penny? FAQ

Rules & reminders

Keep it simple. Keep it true.

Receiver has authority

Only the receiver can finalize acceptance. This stops phantom deliveries.

Vouchers are not postage

Never call them “stamps.” Use voucher / delivery credential terms only.

XP is cooperative accounting

XP records participation. This portal is non-custodial and does not hold your money.

Tip: If you are not registered yet, register your device first so your scan can be trusted and credited.

Scan #2 • Acceptance

Confirm delivery (receiver acceptance)

This is the receiver’s confirmation page. Wire it to your backend endpoint to post the finalized ledger entry. In production, the system should validate: registered device witness, voucher ID, expected receiver, timestamp, and (optional) location if enabled by policy.

Voucher / delivery credential ID

Use the ID printed on the delivery credential attached to the package.

Receiver (you)

The receiver is the final authority on acceptance.

Is this the final destination?

Final destination enables settlement + service recognition rules.

Condition on arrival

This helps route disputes without breaking the ledger’s truth.

Final delivery person (if known)

Used to mint a New World Penny service award when final destination is confirmed.

How many hands touched this delivery?

Optional: record in-route handoffs for transparency and recognition policy.

Delivery location (optional)

Optional. Only include if you opted in to location during scans.

Your Peace Pentagon branch

Branch is part of your membership role assignments.

Visible acceptance note (optional)

Keep it factual and respectful. This can be visible as part of the recognition culture.

I confirm the delivery credential ID matches what is on the package.

I understand Scan #2 is the receiver’s acceptance and finalizes the ledger entry as XP.

I understand XP is cooperative accounting (not money) and this portal is non-custodial.

New World Penny FAQ

Ledger preview (demo)

This shows what a clean, append-only “acceptance event” could look like before it is posted.


{
  "type": "POD_ACCEPTANCE",
  "voucher_id": "YAM-POD-000123",
  "receiver": "Receiver ID",
  "final_destination": true,
  "condition": "good",
  "hands_touched": 1,
  "branch": "distribution",
  "timestamp": "auto",
  "location": "optional",
  "recognition": {
    "new_world_penny": true,
    "awarded_to": "Final Delivery Person"
  }
}

Measurement note: XP may be expressed using the reference convention 21,000 YAM = $1 USD for reporting. This is a measurement yardstick for cooperative accounting, not a custodial promise or immediate redemption guarantee.

Human Blockchain

Menu