Open academic research · $0 / recognition-only

ENTITY Academic Research Challenges

Public, bounded research problems for students, labs and independent researchers. Counterexamples, negative results and incompatible interpretations are welcome.

No paid bounty: there is no cash, cryptocurrency, token, gift card or other financial reward. Credit may include public attribution, normal contributor history, merged work, and links or citations to independently controlled research artifacts.

Open challenge hub Contribution workflow Conformance boundaries

Research tracks

Formal verification

Model authority, rights, events, replay identity and fail-closed behavior using TLA+, Alloy, Coq, Lean, Isabelle, F*, Dafny, PRISM, CSP/FDR or comparable systems. Identify provable invariants, false invariants and underspecified semantics.

Distributed systems

Test recovery, replication, portability, restart, duplication, reordering, stale state, concurrent mutation and partition behavior. Fault models and reproducible counterexamples are useful outcomes.

Digital identity & credentials

Compare ENTITY identity, authority, delegation, provenance and recovery semantics with established DID, verifiable-credential and OpenID-style models. Document semantic matches and mismatches.

Cybersecurity

Investigate replay, evidence substitution, confused-deputy behavior, authorization scope, rollback, key/recovery boundaries and malicious inputs using public artifacts only.

Software engineering & reproducibility

Reproduce public campaigns from clean environments, test portability across six language baselines, improve onboarding, or build independently authored conformance tooling.

Suitable academic formats

BSc/MSc capstones, formal-methods projects, security labs, distributed-systems experiments, research-methods assignments, software-engineering reproducibility studies and thesis scoping where a university supervisor approves the work.

Evidence rules

State the exact source tag or commit tested.
Do not change expected vectors or hashes to force a pass.
Separate observed behavior from interpretation.
Publish enough environment and method detail for reproduction.
Keep independently claimed work in an independently controlled repository.
Do not treat a BTG-reviewed merge as automatically independent validation.
Report counterexamples even when they contradict project expectations.

Public starting points

ENTITY source · External verification · Standards/interoperability review · Clean-room implementation