Files
triangles-explorer/.env.example
T
Krystie b4c5b1beb4 feat: add Verified Dev Contact badge + /verify route for signed messages
- Add 'Verified Dev Contact' badge on the address page when the address
  matches the official dev contact (TRsiRzkMWm87ZuWFwPB8YXFGYr5AQZo7fb).
  Badge includes the signed message + signature, collapsible by default.
- Add /verify page with a form that takes address + signature + message
  and calls the daemon's verifymessage RPC to re-verify.
- Add /api/verify server endpoint (POST) that calls the daemon's
  verifymessage via JSON-RPC and returns { valid: boolean, error? }.
- Add 'Verify' link to the main nav.

Dev contact proof (verified on DNS2 v5.9.23 mainnet 2026-06-23):
- Address: TRsiRzkMWm87ZuWFwPB8YXFGYr5AQZo7fb
- Message: 'ROGER THAT, TRIANGLES DEV ADDRESS IS A GO.\n\n5.9.23 IS LIVE.'
- Signature: H/gT/bFSL+WFT4F4WYPvDIVAnt0/M2WQy/ypUvhMtdXgAop+Euycakif9QERNcUfPLNF29vDxuXZf1BJjd8Snro=
2026-06-23 17:24:31 -07:00

7 lines
216 B
Bash

TRIANGLES_API_URL=http://127.0.0.1:19112
# JSON-RPC credentials for the /api/verify endpoint (daemon's verifymessage)
TRIANGLES_RPC_URL=http://127.0.0.1:19112
TRIANGLES_RPC_USER=trianglesrpc
TRIANGLES_RPC_PASSWORD=