BC.Game
No verifiable licence published
28/100, F
0, walk away100, pays reliably
What we check
PayoutsNot enough payout reports yet
Player complaintsNo recent complaints on file
Site legitimacyDomain not checked yet
OversightNo verifiable licence published
Recent activity
Aug 5, 2026 Score recalculated, 28 grade F
Audit ledger
Each time this score is calculated the inputs are sealed into an append-only ledger and hashed. The record below is the current one. Recompute the digest yourself and it has to match, or our arithmetic is wrong.
Digest (SHA-256)15b49b7ec6a0…
SealedWed, 05 Aug 2026 17:27:37 GMT
Algorithm version2.1
Show the sealed record and verify it
This is the exact JSON that was hashed, with keys sorted, which is how it is canonicalised before hashing.
{
"casino": "BC.Game",
"evidence_coverage": 55,
"grade": "F",
"pillars": {
"blockchain": 10,
"domain": 5,
"license": 3,
"operational": 9,
"sanctions": 12
},
"score": 28,
"timestamp": "2026-08-05T17:27:37.142Z",
"version": "2.1",
"weights_applied": {
"domain": 20,
"license": 15,
"operational": 20
}
}
Full digest:
15b49b7ec6a07eb3cd8a3da8490b17c33b57311d8ac798ebcc913ef95397b3d8
To check it, hash the canonical record with keys sorted and no insignificant whitespace:
node -e "const c=v=>Array.isArray(v)?v.map(c):v&&typeof v==='object'?Object.keys(v).sort().reduce((a,k)=>(a[k]=c(v[k]),a),{}):v;
const p=require('./record.json');
console.log(require('crypto').createHash('sha256').update(JSON.stringify(c(p))).digest('hex'))"
Last checked Wed, 05 Aug 2026 17:27:37 GMT. Scores are computed from recorded data by the same algorithm for every operator.
How we score.
Niekie carries no affiliate links and links to no operator, so there is nothing here that can pay us for a click.