r/Hedera • u/Intelligent-Orchid34 • 7h ago
r/Hedera • u/Intelligent-Orchid34 • 14h ago
Discussion Fed Governor Chris Waller says the bank monopoly in payments is “breaking down” as blockchain and tokenization push traditional finance to compete with new entrants.
In prepared remarks at The Clearing House’s annual conference this morning, Waller said he sees stablecoins, tokenized deposits and traditional payment rails coexisting, with the private sector driving innovation.
But he says scaling tokenization will require clear answers on who’s responsible when things go wrong like lost keys, smart contract exploits and assets stranded on “zombie chains.”
r/Hedera • u/DocumentFair4693 • 16h ago
Discussion Nillion joins the DeRec Alliance + BankSocial delivers first live implementation for banks & credit unions
Hedera just welcomed nillion to the DeRecAlliance.
BankSocial (@BANKSOCIALio) has also delivered the first production implementation of the DeRec standard, bringing secure decentralized recovery to thousands of bank and credit union users.
DeRec is the open recovery standard co-founded by Leemon Baird and backed by Hedera, Ripple, Algorand, Input Output, and others. It lets users recover keys/secrets via a threshold of trusted helpers instead of relying solely on a seed phrase.
Sources:
Official Hedera post: https://x.com/hedera/status/2122696152130699697 BankSocial announcement: https://news.banksocial.io/derec-recovery-standard/ DeRec Alliance: https://derec.org/
r/Hedera
•
u/HBAR_10_DOLLARS
•
1d ago
Discussion Ħ The entire crypto market is experiencing a complete meltdown. Hedera and $HBAR are positioned better than ever to rise from the ashes. This is our moment and we are fully prepared to meet it. Ħ
First, let's put things into perspective.
Crypto sentiment is in the gutter, the worst I've ever seen it. Go check out the communities and see for yourself what type of discussions they are having:
Bitcoin - BTC is in crisis mode because the whole technology relies on Number Go Up, and the number has not gone up much these last 5 years. People don't care about it, the Bitcoin reserve thesis has stalled, and AI has sucked all the energy out of the room. There hasn't been a Bitcoin mainnet upgrade in over 5 years. Michael Saylor is the only one buying in large quantities, and the more coins he holds the more uncertainty he adds.
Also, and this is very crucial: there is still no solution to post-quantum security and the vulnerable early wallets (and quantum timelines are moving up with assistance from AI).
Ethereum - No direction at all. For years, Ethereum thought leaders were telling developers to build on layer 2 networks as a scaling solution (essentially different networks that occasionally write back to the Ethereum mainnet). Now, they are telling them to come back to the layer 1.
But all of the layer 1 problems remain (highly variable gas fees, frontrunning, can't scale, 10+ minutes for real finality), and current timelines for "Lean Ethereum", another complete overhaul of the network, go into 2030. You can't outrun this much technical debt.
Solana - Meme coin casino network, memes are dead, not much else to say here. The network is experiencing an inflation and frontrunning/MEV crisis as the remaining validators extract as much value as they can from dwindling network activity.
Cardano - Charles Hoskinson is on video recently saying that "Cardano's roadmap is complete, everything I said is going to be built has been built." $ADA price is 15 cents with an all-time-high near 3 dollars.
https://x.com/DegenerateNews/status/2121130289108054440
These are only a few coins in the top 20. Dig a little bit deeper. Find the coins which have dropped out of the top 50, or out of the top 100. Check in on their communities, see what type of news and developments they have had this year, and see what discussions they are having.
You may also stumble upon some of communities/networks/protocols which no longer exist because they have already closed down.
I would also like to quickly reiterate that Leemon predicted all of this nearly a decade ago. We are living through it today:
“Typically, the history of any kind of market is that you have this enormous springing up of thousands and thousands of companies, and then you have a crash, and then you get down to three or four big companies that continue.” - Dr. Leemon Baird in 2017.
Now, let's take a quick look at Hedera. We all know what type of discussions have been going on in this community. But let's focus on the network development these last few years, broadly:
CLPR.
Block nodes/Streams.
HashSpheres.
Dozens of HIPs (Hedera improvement proposals).
And a very strong and healthy Council pipeline, despite some claims to the contrary.
And if we look a bit further up the stack we can see complete end-to-end solutions like Asseto, going to market, with APIs that easily integrate into any enterprise tech stack. These are finished solutions which are quite literally ready to scale their usage by 1000x or more.
The point is this:
We were always going to have to experience this correction. There are far too many networks and protocols.
It doesn't make sense for hundreds of different networks to be adopted; it makes sense for a few of them to be very successful, seeing widespread adoption and strong network effects.
That being said, I will leave you with a quote from just this last month.
"Brief recap of Swift’s SIBOS Miami. 4 days, 100+ global banks. Only Hedera+Ripple+Quant+Chainlink in the room." - Greg Bell, CIO at Hashgraph.
The crypto market is melting down around us. But Hedera is stronger than ever, and my HBAR bags larger than ever. I am ready.
r/Hedera • u/DocumentFair4693 • 1d ago
News PwC US and Hashgraph Collaboration: Why AI and Stablecoin Roadmaps Must Converge
r/Hedera • u/cSigmaFinance • 1d ago
Meme Builders on Hedera aren’t just solving today’s problems, they’re building for the long run
Making Finance Better!
r/Hedera • u/DailyUpsAndDowns • 3d ago
Discussion Stuff Your Bags People!
I can even begin to imagine the level of FOMO we're going to hear from the absolute masses of people who woulda, coulda, shoulda bought more. Be it HBAR or BTC or anything. The begging for price to go under 0.06. The golden opportunity to lower your average. This is the Godsend moment we're been very patiently waiting for. Lick it up baby, lick it up!
r/Hedera • u/_BeeSnack_ • 3d ago
Meme Not even my ex dumped me this hard
Anyways, there is opportunity
r/Hedera • u/Terrible-Grass6136 • 4d ago
Discussion HBAR below 6 cents
Congrats to the FUD squad. HBAR is now in the 5s. You won.
r/Hedera • u/Substantial_Data2707 • 4d ago
News Next Hedera mainnet release (v0.79) will switch to block nodes & block stream
This is a big deal from a cost perspective.
Up to now each Hedera consensus node has to push a record file & a sidecar file to Google Cloud AND Amazon S3 bucket, every ~ 2 seconds.
This is roughly 63 million records & sidecar files PER YEAR per consensus node.
There's about 30 nodes. So that's nearly 2 billion record & sidecar files being uploaded to Google Cloud AND Amazon S3 bucket every year. 👀👀
Imagine the ongoing cost & storage fee Hedera has to pay for the cloud buckets.
Furthermore, the mirror node provides has to query (LIST) the files and then downloads most if not all records to reach majority (>33%) and super majority (>66%). This is also costly for the mirror node operators. I used to run a mirror node but not anymore because it was expensive (>$2000 USD per month). That will change in the future with the introduction of block nodes on mainnet.
After the next mainnet update (18th Nov), the remaining ongoing cost is the storage of the legacy record & sidecar files on the cloud buckets. At some point there'll be a HIP to address this (moving the records off the cloud servers, and possibly preserve them as a block stream format). After that is done, the hidden and ongoing cloud storage cost will drop to $0
See https://hedera.com/blog/block-streams-replace-the-record-stream-by-default/ for more info.
r/Hedera • u/No_Performance6081 • 4d ago
Discussion Most Bearish of all signals
Charles Adkins backslide from Hedera Foundation CEO to part real estate salesman part wanna-be influencer has to be the most bearish of all signals. Only reason guy has a following is bc of Hedera and he’s very sadly attempting to capitalize on that following to promote.. what , exactly ?
The fact he was hired in the first place is a portent of what’s to come.
Keep praying, hedera fam.
r/Hedera • u/HBAR_10_DOLLARS • 4d ago
Discussion Ħ HBAR Weekly Update - Brand New Hedera Council Member...5 to Go! Ħ
r/Hedera • u/Intelligent-Orchid34 • 4d ago
News 🪙 @YieldFX is opening up FX access for emerging-market savers on Hedera. Hold tokenized deposits at regulated banks, switch currencies instantly, earn daily interest, and stake into FLEX, its hybrid FX exchange.
r/Hedera • u/Cold_Custodian • 4d ago
Developer CLPR Change Watch: November 12, 2026
Changes since the November 11 report, checked through early November 13 UTC.
The revised fee model and EVM Channel-binding fix have merged into Hiero main. Development also exposed a remaining backlog-delivery limitation and a broader TSS verification requirement. These are meaningful advances and newly documented gaps; they do not establish production readiness.
TestLens totals below are repository-wide CI counts, not exclusively CLPR tests.
1. Connector economics and revised network fees are now merged
On November 12, PR 28137 merged as 0b246914. This changes the previous finding: the revised economics are now implemented in main, although the author explicitly says the prices remain temporary pending confirmation.
Connector capital and penalties. The minimum bond changes from the earlier 1 HBAR default to a $3,000-denominated minimum, converted into HBAR at the active consensus exchange rate when Connector registration is completed. The deposited bond remains recorded in tinybars; existing stakes are not continuously revalued. The first slash is $10, converted at the applicable exchange rate, with escalating penalties and forfeiture of the remaining stake on the fifth offence.
Endpoint compensation. For a newly dispatched DATA message, the implemented Connector reimbursement becomes actual callback gas cost + 0.01 HBAR + $0.01 converted into HBAR. The dollar-denominated progress reward replaces the previous percentage margin. Response callbacks reimburse actual gas without the DATA compensation. These payments go to the submitting bundle payer; slashing proceeds also compensate the submitting endpoint. Merged economics documentation
Network pricing. Implemented service base prices include $100 each for Channel registration and completion, $10 for Connector registration, and $25 for Connector completion. sendMessage has a $0.10 target including its gas, with an additional byte charge beyond the included allowance. The two HAPI proof queries become paid queries. Applicable byte, verification and other charges mean these base prices should not be treated as all-inclusive quotes.
The merged schedules retain free ClprEndpointPublication and exempt ClprSubmitBundle from separate node/network fee components while retaining its service, byte and verification charges. The 1,000 HBAR nodeSubmitBundleMaxFee is a maximum offered fee, not a per-bundle tariff. Merged fee schedule
This merge also adds the missing CLPR entries to the upgrade schedules. The separate PR 28225, reported yesterday, was closed without merging. TestLens reports 48,790 tests passing for the fee PR’s final head. CI result
Economic/HBAR interpretation: This makes the potential capital requirement and payment flows considerably more concrete. Public-Hedera deployment and usage would require public HBAR for the relevant balances, bonds and payments. Private-network currency remains economically separate. Connector reimbursement is distinct from network fee revenue, and neither automatically constitutes Hashgraph revenue. Application-facing Connector pricing is still unspecified, and proportional recovery of shared bundle-submission fees remains described as planned work.
2. EVM Channel binding is fixed in main; oversized backlogs remain a delivery problem
On November 12, PR 28147 merged as ff14a176.
Ethereum, Sei and QBFT verification now bind proven storage keys to the Channel selected locally and check the peer service address against the trust anchor. A valid proof belonging to another Channel cannot satisfy these checks merely because its counters and running hashes match. Duplicate, missing and unrelated storage keys are rejected. TestLens reports 26,905 tests passing. Merged implementation · CI result
This resolves the implemented EVM storage-key binding gap. The separate Hiero Channel-leaf binding fix, PR 28191, remains open, as does the broader QBFT quorum and anchor redesign.
A new November 12 issue 28255 documents a separate liveness limitation: Ethereum, Sei and QBFT verifiers cannot currently accept a bundle ending before the sender’s queue tail.
For example, if messages through 49 are queued but a capped bundle carries only 11–30, the verifier and handler cannot reconcile that partial bundle with the tail’s metadata. The proposed correction would authenticate and return metadata for the bundle’s own last message.
The issue explains that rejection already occurred before the Channel-binding merge; the new checks reject it earlier. The security fix therefore does not resolve backlog draining. The proposed remedy remains unimplemented, with acceptance tests still outstanding.
Implication: Proof isolation improves, while delivery under sustained backlog remains an operational gate. This matters directly to applications and Connectors relying on timely execution.
3. TSS rotation consistency improves, while external threshold enforcement needs coordinated work
On November 12, PR 28215 merged as 9e0de396.
It corrects inconsistencies between WRAPS address books and hinTS participant sets when some roster members are omitted from the signing scheme. Complete ordered membership and weights are preserved for each generation, with changes to restart recovery, unfinished attempts and signer eligibility. The author reports 699 targeted tests passing, including native proof-generation and rotation scenarios, but explicitly reports no live-network run.
This advances trust-anchor rotation and recovery. It preserves completed trust roots rather than automatically replacing them.
Separately, the new PR 28248 proposes measuring preprocessing and block-signing thresholds against the complete committed generation weight, including omitted members. It remains open. Its current CI reports 26,031 tests passing, with the Codeowners check outstanding. CI result
The important remaining gap is external verification. The current cryptography library’s TSS.verifyTSS authenticates the hinTS key but applies a majority threshold to the weight represented by that key. With total generation weight 20 and participating scheme weight 18, signer weight 10 can pass that scheme-based threshold while failing a strict majority of the full generation.
Issues opened early November 13 UTC now coordinate the required changes across cryptography, consensus-node proof production and CLPR verification, Block Node, and Mirror Node.
The threshold must be authenticated alongside the key, carried through a versioned proof format, and enforced by consumers. Tightening honest-node signing alone does not accomplish that. The proposed stronger thresholds also impose stricter availability requirements on sparse signing schemes. Rollout analysis
Assessment: This identifies a concrete additional requirement for trustworthy Hiero-origin proofs. It is an open protocol and integration dependency, not a completed security fix.
4. Gas-accounting hardening advances beyond the merged fee model
On November 12, the still-open PR 28146 advanced to 11dc7011.
Its updated implementation would preserve actual executed-gas charges when child-call records are cleared during rollback, prevent duplicate verifier charging, apply the aggregate 300,000-unit verifier billing cap, and enforce the signed transaction fee maximum across base fees, byte charges and gas escrow.
It also reserves the bundle payer’s gas funds before reversible Connector reimbursements or slashing payouts can supply those funds. This addresses the ordering of financial obligations within a bundle.
The PR retains its peer-manifest size and endpoint-count protections. TestLens reports 63,876 tests passing, with Codeowners approval outstanding. CI result
Economic implication: The fee merge establishes prices and transfers, while this separate proposal continues to harden who pays, when funds must exist, and what remains payable after failure. Reimbursement correctness is therefore still undergoing review.
5. New proposals tighten transport and message limits
Several November 12 proposals address resource consumption and endpoint operation. All remain open.
PR 28260 validates outbound peer destinations, uses numeric IP addresses without DNS resolution, and requires explicit configuration for additional private or local address ranges through clpr.additionalPeerEndpointCidrs. It also adds bounded retry delays and resets them after successful exchanges.
That proposal does not yet have clean CI. TestLens reports 20,969 tests executed with one failure: CLPR log validation encounters rejection of a test peer at 10.0.0.1. This exposes configuration/test integration work still needed around the new restrictions. Failure report
PR 28261 changes payload-size enforcement to measure the complete serialized DATA message—including routing fields and protobuf framing—instead of application data alone. Checks apply before outbound queue writes and during inbound bundle validation. Messages close to the previous data-only limit may consequently need adjustment; Response and Control exemptions remain.
PR 28247 bounds peer-requested bundle construction using local limits, while preserving enough capacity for one admitted message and its proof. PR 28237 replaces remotely exposed parser exception details with a fixed invalid-payload error.
Assessment: These proposals improve resource control and operational resilience. They do not establish per-Channel mTLS authorization, measured throughput or production-scale performance.
6. Canton review fixes acceptance differences and explicitly records remaining gaps
On November 12, the open Canton verifier PR 28205 advanced to 7025b2ed.
Review-driven changes add validation for explicitly supplied Connector IDs, preventing non-32-byte values from being accepted where the Solidity reference rejects them. They also make confirmer-weight arithmetic overflow-safe and document an intentional Ed25519 difference: the native implementation rejects small-order keys that the referenced Solidity implementation accepts. Review-fix commit
The updated PR description also explicitly defers checks involving verdict wire types, non-minimal varints, invalid protobuf field numbers and certain noncanonical DER encodings. This qualifies the earlier description of the parser as uniformly strict. Trust-anchor rotation, configuration verification and topology changes remain future work.
Current CI reports 27,445 tests executed with one hook/stream-parity timeout. That result does not establish a Canton verification regression, but it is not an all-green run. CI result
Implication: Native Canton support is receiving substantive compatibility and security review. It remains an unfinished integration, with no demonstrated commercial traffic or attributable HBAR revenue.
7. Interoperability tests, operator tooling and application integration progress
Compact Hiero proofs. On November 12, PR 28181 reached 24261549, with 63,558 tests passing and all 53 reported checks completed. This supplies current-head CI evidence for the proposed compact-proof and witness-chain integration. The PR remains open; the count is not a throughput benchmark or independent audit. CI result
Operator key handling. Late November 12 US time, PR 28163 strengthened its identity-tooling proposal. Signing scripts reject inline private keys, use separate key files, check POSIX ownership and permissions, and reject symlinks. Existing output files are backed up, and bundle-generation failure handling avoids leaving a newly written unmatched key. It remains open; 26,646 tests pass, with Codeowners approval outstanding. Changes · CI result
Mirror Node fixtures. November 12 changes to PR 14636 replace older captures with local alpha5 block fixtures and add the missing Channel-registration block. Tests now explicitly follow the pending commitment from registration through completion and historization. This addresses gaps in the previously described fixture evidence. The PR remains open; these local captures do not establish public-network usage or complete receiving-side coverage. Fixture update
SDK acceptance. The November 12 update to SDK design PR 290 consolidates eight HAPI transactions, two paid proof queries and two Mirror Node lookups into its proposed Phase 2 scope. It explicitly distinguishes offline compatibility from live acceptance, and requires application callback or state evidence rather than queue counters alone to establish delivery. Final signing/consent contracts, release alignment and live fixtures remain acceptance gates.
Together, these developments improve integration readiness and evidence quality. They do not yet demonstrate a finished, released cross-ledger application stack.
8. LFDT organization discussions open; deployment and commercial evidence remain unchanged
On November 12, Edward Wertz opened LFDT specification issue 7 seeking stakeholder input on repository organization: retain the current arrangement, consolidate into a monorepo, split by ledger, or adopt a hybrid. His subsequent comment favors evolving from the existing structure as specialized implementations require it. This is a discussion, not an adopted migration or protocol revision.
The HIP and the LFDT specification, smart-contract and endpoint heads remain unchanged from the previous check. No new releases or tags appeared in those three LFDT repositories.
The official network status still lists Previewnet at v0.80.0-alpha.5, Testnet at v0.79.0, and Mainnet at v0.78.2. The new main merges therefore should not be presented as evidence that these fixes or fee settings are already deployed on those networks. Hedera network status status.hedera.com
No new public primary-source evidence was found of an independent CLPR audit, production benchmark, commercial Connector operation, attributable Hashgraph revenue, cross-ledger liquidity, or public-HBAR value capture.
r/Hedera • u/Choice_Employee_7739 • 4d ago
Discussion New to Hedera and trying to understand Hedera's new agent accounts
Pretty new to Hedera, and Agent Accounts are one of the first features I’ve come across that I can picture using in everyday life. The idea of giving an AI agent a capped account with approved recipients makes sense to me for paying for things like online services.
What I’m trying to understand is HBAR’s role when a payment could also be made in USDC. I know HBAR is used for network fees, but could agent payments create meaningful demand for HBAR beyond that, or would most of the activity depend on which token the service accepts?
Since this is still in the testing roadmap, I’d wait to see a real app using it before adding to my HBAR exposure. If I do, I’d make it a small HBAR spot order rather than treating the announcement itself as a reason to rush in.
What kind of small, everyday payment would you actually trust an agent account to handle first?
r/Hedera • u/Intelligent-Orchid34 • 5d ago
News BankSocial and CEO John Wingate (@PresidentHODL) have received a 2026 Global Recognition Award for Innovation. 🏆
Out of 15,000+ applicants worldwide, only 5.8% were selected.
Here’s what sets our open-banking architecture apart: ⚡ Native to u/hedera for instant finality & micro-fees 🛡️ 2M+ settlement events with 0 security breaches 👥 40% reduction in credit union deposit leakage for members under 35 📱 True self-custody with zero seed phrase friction
Huge thank you to John and the entire BankSocial team! 🚀
r/Hedera • u/RangeSea7591 • 6d ago
Poll Poll: Should the lawsuit post be removed?
Edit: By 'Take it down' I mean Unpin. Apologies for the confusion.
Trying to maintain a balance between respecting the wishes of the community VS being transparent regarding the issues Hedera is facing.
I'm certain nobody wants see this place turn into a crypto version of r/Superstonk (a circle jerk).
Since there's been a lot of emotions and bickering lately (understandably) I just want to remind people not to take Reddit too seriously. Ultimately this sub will have zero impact on Hedera's eventual success or failure.
Entertainment, not education.
r/Hedera • u/crypto_zoologistler • 6d ago
Discussion Arb bots have been driving most of the tps growth recently
I’ve seen a few posts (and some confusion) recently about the huge traffic going to certain nodes, mainly Accenture, NSE and Dentons. Almost all this traffic is from a handful of arbitrage bots (two in particular).
These bots are Cyclebot, run by a Grelf enthusiast (I know who it is but I won’t name them here) and OnlyFlies bot, run by the creator of the FLY memecoin.
Over the last month these two bots have accounted for ~40% of total tps and ~10% of total fee revenue. About 75% of the tps growth we’ve seen since August comes from just these 2 bots.
Cyclebot has made its owner about 60k HBAR profit over the last 3 months.
The way arbitrage works on Hedera is really different than most other networks because there’s no mempool on Hedera and no way to pay to front-run, on Hedera arbitrage is all about speed - it’s a race not an auction.
This need for speed is likely why these bots ping consensus nodes so much, they’re trying to figure out which node is processing transactions the fastest.
I go into a lot more detail and cover all the on-chain evidence in my full deep dive which you can read at the link below 👇
r/Hedera • u/drjrocksforever • 6d ago
Discussion Please Un-Pin the Hedera THA Lawsuit Post
It was helpful to inform the community about this development. But it is old, stale news, over a month old. I don't think this or any similar Reddit site should lead with a negative story about their own network for very long - that is, unless the moderators don't believe in the future of Hedera and want visitors' first impression to be a negative vibe without the news being cast in the larger context of its relative importance. Oldtimers got the news day one and newcomers should be greeted either with something helpful and positive if something is going to be pinned. or they should be greeted with whatever current post merits top billing solely on the criteria by which all other posts rise or fall in the queue. Just my opinion.