finalis
100 posts

finalis
@finalis_core
Deterministic Finalized-State UTXO System
World Присоединился Nisan 2026
127 Подписки31 Подписчики

🚀 Major Stability Update Released
Fixed:
• Startup failures & diagnostics
• Deterministic settlement canonicalization
• Round-0 liveness issues
• Validator endpoint persistence
• Telemetry & CLI tools
All validators should pull latest main, rebuild, and restart.
This is an important upgrade for network health.
$FLS #FinalisCore #BFT #opensource #crypto #altcoin
English

🎉 Big Milestone!
The first validator has officially joined Finalis Core.
They burned 400 $FLS to become a validator.
The path to true decentralization has begun 🔥
We’re now looking for the next validators.
Who’s joining next?
Onward.
$FLS #FinalisCore #FLS #BFT #Decentralization
English

**What We Fixed:**
• Startup reliability & better diagnostics
• Deterministic settlement canonicalization (no more frontier commitment mismatches)
• Round-0 liveness improvements (reduced unnecessary timeouts)
• Persistent validator address management (`validators-addrman.dat`)
• Cleaner runtime disagreement telemetry
• Enhanced CLI debugging tools
English

@NastiaVox Artificial resources cannot replace natural resources. I think it will replace paper money. But I don't think Bitcoin will be able to do it.
English

We could’ve just said the security tip.
But where’s the fun in that?
Crack the Code and Comment down below.
#WorldPasswordDay #BinanceIndia #CryptoSecurity

English

@KhalidAlNumi Put it in a consensus that is a stand-alone L1 quantum resistance and can also directly exchange transactions without touching bitcoin L1. That would make your brain boil.
English

finalis-core consensus is deterministic committee finality over height+round.
Core flow:
1. Height/round model
- Chain advances by finalized transitions at height `h`.
- For each next height, protocol runs rounds `r=0..n` until a proposal gets quorum.
2. Committee derivation
- Active validator set is derived from validator registry state at that height/epoch boundary.
- Non-active states (exiting/suspended/banned/onboarding/pending per rule path) are excluded from effective voting committee.
- Committee snapshot is deterministic and persisted/frozen by epoch logic.
3. Proposer/leader selection
- For `(height, round)`, proposer is deterministically selected from committee.
- If proposer is missing/disconnected, timeout path advances round.
4. Proposal validation
- Nodes validate proposal structure, parent/finality links, state transition commitments, and policy constraints.
- Invalid proposals are rejected; valid ones are voted.
5. Voting and quorum
- Validators sign votes for valid proposal/finality objects.
- Quorum threshold is computed from active committee size (`2n/3 + 1` in current code path).
- Only committee-member signatures count toward quorum.
6. Timeout certificate (TC) and liveness
- If proposal/votes stall, validators emit timeout votes.
- Quorum timeout votes form a TC.
- TC moves protocol to higher round, allowing fallback proposer and re-vote without violating locks.
7. Finalization
- Once quorum signatures are collected for the canonical object, block/transition is finalized.
- Finalized data (transition, certificate, indexes) is written to DB; tip advances.
- Next height repeats with updated state/committee inputs.
8. Safety properties (intended)
- Deterministic derivation + quorum signatures prevent arbitrary forks under assumptions.
- Non-committee signatures do not inflate participant count.
- Lock/round rules + TC reproposal preserve safety across retries.
9. Validator lifecycle interaction
- Register/bond/onboarding affect future eligibility/activation.
- `ACTIVE` validators participate in committee/quorum.
- `EXITING/SUSPENDED/BANNED` are excluded from effective active set, reducing committee/quorum size accordingly.
10. Operational overlays (not consensus rules)
- Snapshot fast-sync, reindex/repair, turbo ingest, RPC onboarding are node ops only.
- They should not alter proposal/vote/finality validity rules.
#BFT #consensus #deterministic #committee #finality
English

@orangementality @SimplyBitcoin This is more like a joke. I think it's more of a distraction than remembering the password.
English

@finalis_core @SimplyBitcoin How did he crack it? Maybe he forgot the password of the computer and not the bitcoin?
English

@finalis_core @SimplyBitcoin @GavinAnderson12 the wallet.dat is/was created on install correct.
If you took that wallet.dat and put it in a password protected zip file, you've effectively encrypted the compressed file with a password. Doesn't matter the client's capability. That's my point.
English













