Skip to content

assmore22/beacon

Repository files navigation

Beacon

Claim markets where both sides have to leave a public trail.

Beacon is a claim desk for disputed public statements. It combines stakes, evidence and GenLayer review so a YES or NO outcome is tied to sources rather than a private moderator.

Review Links

Surface Link
Live app https://assmore22-beacon.vercel.app
GitHub https://github.com/assmore22/beacon
Contract https://explorer-studio.genlayer.com/contracts/0x770Db6D01D1fC69d045ecB208DA669b977c3ee5E

Chain Record

  • Network: GenLayer Studionet
  • Chain ID: 61999
  • Contract: 0x770Db6D01D1fC69d045ecB208DA669b977c3ee5E
  • Deploy transaction: 0x8714ccf0...012319
  • Deployed: 2026-06-23T23:51:13.565Z
  • Source: contracts/beacon_v2.py (45,907 bytes)

Protocol Path

  1. Define a claim standard.
  2. Open a claim with obligations.
  3. Let both sides stake and attach evidence.
  4. Run validator review.
  5. Handle challenge, appeal and archive state.

The frontend reads claim lists, stake totals, challenge windows and party records. Contract state is public; write actions still require a connected wallet on GenLayer Studionet.

Finalized Smoke

Action Transaction
set_claim_standard 0xcd41bc9a...3491e5
open_claim 0xacee5f3c...d33cf1
add_obligation 0x01c745e3...a852c8
add_evidence_docs 0xf824b50e...d6607a
add_evidence_web 0x9b03bbe3...bd2ca3
stake_yes 0x4a48854b...ab1347

Local Run

python -m http.server 8080

Open http://localhost:8080.

Release Hygiene

The public package is static and has no install step. Vercel receives only frontend, contract source and public deployment metadata.

Keep wallet private keys, vault exports, .env files, Vercel project state and dashboard data out of Git. This repository is for public source, UI, tests and deployment receipts only.

About

Public signal attestations with finalized GenLayer validator reasoning.

Topics

Resources

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors