finalis

@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.

Where should I put 50K? Give me the ticker.

@FezWeb3 On March 15, there were a maximum of 500,000 bitcoins in existence. Where did that many come from? Hmm

Do you think she's still holding?

@FezWeb3 Fake video

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

@nickisanders Both

Ethereum or Solana?

@rodpalmerhodl The beginning of a new stimulus

today I was fired from coinbase. i was responsible for making the site go down anytime the bitcoin price was pumping.

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

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

A 22-year-old student in Norway spent $26 on Bitcoin in 2009. Forgot the password for four years. When he finally cracked it, his 5,000 Bitcoin were worth $886,000.

@tempstat @SimplyBitcoin @GavinAnderson12 It's a wonderful discovery. It seems logical.

@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.

@kit_sats Soon #finalisCORE will be added to this odd list. 😊

bitcoin is the only thing I’ll buy while it’s going down

@tempstat @SimplyBitcoin In the original versions from 2009, the .dat binary file was created by itself. Until @GavinAnderson12 updated it on GitHub.. I don't believe this story. This is Amy's opinion.

@finalis_core @SimplyBitcoin Date is kind of irrelevant to your statement about 64 hex string, without more context from the original post. Anyone could encrypt their 64 string inside or outside of the client. They said password, so i'm making the assumption this is the case. maybe i'm misunderstanding

@tempstat @SimplyBitcoin I know all this. The year is mentioned there as 2009. If it had been mentioned as 2010, I would have believed it. Do you understand?

@finalis_core @SimplyBitcoin No, password not private key. You can encrypt your privkey with a password of any size in the original bitcoin client

@SimplyBitcoin The whale is fighting.

First they said Bitcoin was for criminals. Then they said it was for speculators. Then they said it was for institutions. Now they're applying for the ETF. The story keeps changing. The asset doesn't.

@lourdesanchezok Time to buy lisening intuition )

Time to buy ___ ?? 👀

@CoinMarketCap Nobody's talking about finalisCORE, but this year they will be LISTED.

Nobody's talking about ______ but this year they will be.

@Davincij15 Don't think about the past. Be present.

I could have owned 100,000 #BTC in 2011 but I didn't go all in. I regret that.

@schmidt1024 Friends, FinalisCORE is being created to solve this. Bookmark it so you don't miss the listing. Or run the network now

A Monero is a Monero A Bitcoin is sometimes a Bitcoin and sometimes a legal problem

@eirikapex - Monero: 25,891 nodes - Bitcoin: 21,000 nodes - Finalis: 13 nodes @grok Re-check this info every year.

Monero: 25,891 nodes Bitcoin: 21,000 nodes The “small privacy coin” has more decentralization than the king itself let that sink in

@alanbwt @halfin We miss you.

Happy birthday Hal

@kit_sats True. It was developed for everyone else.

bitcoin isn’t a trade, it’s a test