Filter
Exclude
Time range
-
Near
30 Nov 2025
I think in a few months Beam Warp will be on mainnet, if not earlier, given the updates given by the team, but at least before Solana Alpenglow. Note that Beam Warp nor EVM support is committed to github yet to prevent "copy cats" from taking the code. However you can test it on Dappnet as proof it really exists. It has been deployed therea a few months ago.
1
4
156
I gotta setup the dappnet browser
1
29
9 Aug 2025
So insanely bullish on $HSUITE moving a portion of supply to $XRPL to support the burgeoning application development vertical on the ledger with next-gen dAppNet infrastructure to make building easy. Yes--@HSuiteNetwork is burning a substantial chunk of supply on $HBAR to support native app development on both ledgers. Unified redemption eliminates the need for bridging the assets. While there may be a slight variation in price, that will drive builders to pay for their subscription with the cheaper token. Absolute brilliance. 10/10. Supply shock inbound.
9
20
95
7,042
6 Aug 2025
No. Retail projects > Council/enterprise projects Hashgraph online Hsuite dAppNet Architecture Bridges DEXs Staking platforms Consumer engagement platforms Retail is way ahead of enterprises in building cool stuff everywhere, not just $HBAR. Retail leads innovation.
4
94
28 Jul 2025
Replying to @Lemmeholdsum
LFG If you're into $XRP and $HBAR, check out @HbarSuite enabling dApps on any chain to build on their dAppNet architecture. XRP is the first chain their supporting beyond HBAR.
3
104
11 Jun 2025
Demonstrating the success of $HSUITE on other networks could help Hedera recognize $HSUITE importance as the only token fulfilling @leemonbaird vision for a DappNet. This prompts the question, why don’t Hedera and the Hedera Foundation support it now @hedera @HederaFndn?
1
2
6
235
30 May 2025
So unbelievably pumped for what @SilkDeFiApp is building. Smart contracts are an unnecessary risk and bottleneck for DeFi, which will only ever scale to 300tps for the entire $HBAR network. @HbarSuite's dAppNet architecture enables native-layer efficiency (75x lower network fees), security (the only $HBAR LPs to never be compromised via smart contract risk), and scalability (33x more tps today, 330x at 100k tps). @SilkDeFiApp will demonstrate what can be achieved when this tech is brought to it's full potential with expanded pairs, permissionless farming rewards for token creators, and the UI improvements $HBAR needs to be used by the average retail user--zero slippage, no individual HTS token allowances, and atomic swaps executed by the user (not a smart contract) for exact token amounts and granular token tracking in the receipt. Next-gen DeFi is here and it's orders of magnitude ahead of what is being done on smart contracts. You're participating in the fair token launch for this disruptive DEX, right? It's only available to users and liquidity providers engaging with the community HTS tokens listed on silkdefi.app What does that mean? The token fair launch is not accessible to VCs and large institutions (they aren't holding these HTS heaters). This is for $HBAR community members only. Get in at the ground floor. All roads lead to $SILK. May rewards go out shortly. The next few months will be exciting.
7
21
86
2,625
1 Apr 2025
#HBARSuite is a layer 1.5. It isn't a Dex. Its a dAPPNet created with #SuiteNodes that use the #Hedera native layer to validate transactions. It also doesnt use EVM nor the Hedera Smart Contract Service to accomplish the same tasks needed for complex contracts but instead leverages #Hedera's native layer. Native Speed, No Memory Limitations, like a broken record. Its a leap of Tech that has yet been duplicated. ie #Hedera.
5
21
82
1,946
1 Apr 2025
The work being done by the #HBARSuite Dev team in creating a native dAPPNet and working with Enterprise use cases while the @SilkDeFiApp is working with the Community is a breath of fresh air. Just glad we got the doxed issue put behind us. 🤣 The focus on decentralization, actual use cases, Gov connections, transparency, and true innovation builds that conviction more and more. #HBARSuiteV2 #HSUITENodeRunners
2
12
492
Replying to @beamprivacy
These are my notes about what we discussed about during this -quite technical- Space. I hope I got it all right! 😅 For context about the Beam Warp L2 project, see these two previous spaces: x.com/dbadol2000/status/1875… x.com/dbadol2000/status/1880… 1⃣ About the Beam L2: - Beam Warp (the Beam L2) will be a PoS chain, where validators stake BEAMX (their own, or delegated) and are rewarded with fees (paid in BEAM) and -at least at the beginning- also with DAO rewards (in BEAMX). - Thus, the DAO will need to define how much BEAMX allocate to those rewards, and what will be its distribution schedule on the L2. - Delegated stakes will be managed by simple proportions (i.e. the fees and rewards received will belong to all validators, proportionally to their stake, and within each share they will belong to the users, proportionally to the stake they delegated to the validator). - Also, Beam Warp being a PoS chain, it will need a set of predefined validators to start with. Alex and Vladi propose to use a pre-staking smart contract on the L1, where validator candidates can stake their BeamX before the launch. - This pre-staking operation can also be an opportunity to tweet and publish about the L2 testnet, to have it known. - Moreover, to ensure reliability, we will also need to have a “whitelist” of validators. Those validators will not be able to remove completely their stake for a long time and will be required to monitor both the L1 and the L2 (to ensure proper L1/L2 bridge operation). - Other validators will be able to join too, but the whitelisted ones will ensure the needed chain reliability. - In any case, the total number of validators will be kept limited, so that the speed of the chain is ensured. - A mechanism will be created to define when, how often and how the set of validators can change. - A bridge (ensured by a minimum set of L2 validators) will allow sending L1 confidential assets into the L2. - To ensure identical IDs and avoid collisions, the assets created in the L2 will start at a very high number. - It will work like this: L1 CAs will be sent and locked in a L1 smart contract. L2 validators will monitor it and will then allow a smart contract on the L2 to mint the corresponding CAs (with same ID). - This process only uses features that already exist in the L1. It allows not having to make any change to the L1, which is a constraint we want to keep. - CAs that have been bridged this way, will be able to go back into the L1 through a reverse process: CAs will be burnt on the L2, a transaction will be co-signed by a certain number of validators (among the whitelisted only) and then submitted to the L1 smart contract for unlocking. Note that the signing validators will have to be among the whitelisted ones because the smart contract on the L1 will need to know them so that it can validate their co-signature. - Remark: This capacity of using the L2 validators to pass and validate some information from the L1 into the L2 could even be made generic and extended for other future uses. - Now, on the other hand, CAs created on the L2 will NOT be able to be bridged into the L1 through this king of mechanism. Indeed, since we won’t be modifying the L1, we cannot make it so that the bridged CAs will be created with the same ID in the L1… 2⃣ About the Beam L2 testnet: - As of today, Beam does not have a working testnet anymore (only a dappnet, which is not suitable for this). - Alex proposes to use the L1 mainnet as a basis, and to run a L2 testnet in parallel. Some test CAs will be created on the L1 and bridged into the L2 for testing. During this test phase, the nodes will ensure that only those specific test CAs can be bridged. - It is probable that we will have to incentivize participation to the testnet. And at the same time we will need that testers do commit to certain participation. For that, we can ask candidates to lock BeamX (risk free) and maybe also reward them with some additional BeamX. - The node will be a single binary, which can be configured to be an L1 node only, or also an L2 validator. - If the frontend devs are available, some changes to the wallet GUI might also be done, for easier use.

Replying to @beamprivacy
Another good space today! 👍 Thanks Alex @BeamCTO and Max @maxnflaxl. These are my notes about what was said! Alex started with an announcement: 📢 Beam will be present to the #CryptoXR exhibition and conference (cryptoxr.fr), on Jan 31st and Feb 1st, in Auxerre, France. We didn't get a speaker slot, but we will have a booth, and DB @dbadol2000 will be there to welcome anyone interested in Beam! Also, Alex reminded that if anybody has questions or ideas for the next Space, please do tell him. It can be any subject about Beam, about crypto or about privacy in general. There were two subjects to discuss today: First some comments on privacy tech. And then some of the dilemmas and decisions we have about the upcoming Beam L2. 1⃣ About Privacy tech - The question of the day is: What is an "Anonymity Set"? - The best anonymity happens when we are in the middle of a large group of people behaving the same way as us, and doing the same kind of things. The larger the group, the strongest the anonymity. - That's what a mixer does: it tries to confuse the outside viewers about who is doing what. - We can imagine many people in a room, some want to send money, others want to receive money. If there are only 2, 3 or 4 people in the room, it will be easy to guess who is doing what. But with more people, it becomes more difficult. - But that's not all. Even if there are many people, if you are the only one who is always there, while the other people change constantly, then you will finish by standing out. - This "side effect" idea is very important in crypto, security and privacy. - That's why we need not only a large anonymity set, but a large "effective" anonymity set. - Different coins are using different methods to increase the anonymity set, and hence, ensure the users' privacy. - And to make it simple, we can consider two types of privacy: The privacy of values, and the privacy of identity. - We then see the following, by instance: 1) Beam transactions = privacy of values AND privacy of identity. 2) Beam smart contracts = visible values BUT privacy of identity. 3) Secret Network (TEE-concealed smart contracts) = privacy of values BUT visible identity. - ZCash uses a type of Zero Knowledge Proof, and is probably the best theoretical privacy tech. - Indeed, the theoretical anonymity set of ZCash is infinite. Because when you use a UTXO you prove it's one of ANY of ALL the existing UTXOs! - However, it's not that straightforward. Because not all UTXOs are spent in the same fashion... - By instance, some user might usually spend their UTXOs in one or two days, while another user will keep them untouched for years. The "effective" anonymity set of the former user is much lower because to monitor them, we only need to monitor the UTXOs that "move fast". - Lelantus works in a similar fashion, with the UTXOs in a "Shielded Pool". The difference is that in Lelantus, the size of the pool is not infinite but limited to 64k. - To limit the "side effect" aspect in Lelantus, Beam Wallet tries to automatically use the oldest shielded UTXOs rather than the newest ones, in order to increase the "effective" anonymity set of the user. - Monero, on the other hand, uses a specific and constant number of decoys in each transactions (16 today). - It's fixed but it's enough and it works very well. All the more so that Monero is the most used privacy coin today (which is good as the particular behavior of the user could still appear through the decoys if the overall usage of the coin was low). - In any case, whatever the tech, if you leak info about your transactions (by instance by switching from transparent to private transactions, like in ZCash or LTC MWEB) you will reduce your effective anonymity set. - That's why Beam has privacy transactions ONLY. Now, to the second topic of the day: 2⃣ Decisions about our future L2 - The objective of the Beam L2 is to have a faster Beam alternative (e.g. 1 second block instead of 1 minute). - To allow that, we are going to change the consensus mechanism of the L2 to Proof of Stake (PoS). - Many people don't like PoS because, contrary to PoW, you only need money to make... more money. You don't need to spend any other resource. - And indeed, PoS usually creates a situation where the founders hold a very large share of the coins and of the power. - There is also a problem of "value". Because, in a standalone PoW, the value of the coin is linked to the cost of the resources spent to mine the coins (e.g. the cost of electricity). In PoS, this basis does not exists. - An example of a weakness: Imagine we allow bridging NFTs from ETH into Beam. We can then imagine a very expensive NFT coming into Beam, and an attack on Beam blockchain not being expensive enough to protect that NFT. - The same situation can happen between our L1 and L2, since we want to allow easy exchanges between the two! So we need to be sure that the L2 is not too weak compared to the L1... - For this Beam L2 PoS, we have 3 options: Not use any coin, use BeamX or use a brand new coin. 1) Without any new coin, fees will be the only reward to the validators. If the fees are enough, and the cost of being a validator is low, it can work. - In a few months we will have a proof of concept L2 to play with and we will be able to see how much it's going to cost to be a validator. 2) With a new coin, which cannot be Beam (because its emission schedule on the L1 is already set in stone), we could decide to use BeamX. - Indeed, we have quite a lot of BeamX available. When created, there was a share planned for investors that was not used, and we also have some planned reserve for liquidity and ecosystem incentives. - So the DAO could decide to take some of these coins to reward the L2 validators. And it would make sense because the L2 is a DAO product, and all the applications in L1 will be quickly ported into the L2 and will profit from it. 3) The last option is to create a new coin (codename "BeamW") that would be minted on the L2. Such a scheme would make much sense if it allows bringing investors and external funding, but we are not going to do that. So we will need another mechanism to define the price of this new coin (which will then also allow justifying being a validator). Some last interesting questions that have been raised: a) Who else is building an L2 for their own L1? Do we know any other example? b) If we have a fast L2, why would we use the L1? We need to think about that... c) Can we keep the L1 relevant without artificially crippling the L2 (by instance if we were to only allow creation of tokens on the L1)? Many questions, much dilemas... but a very interesting subject and very exciting times! 🤩
5
19
1,452
27 Feb 2025
This would be relatively easy for a good Tauri/Electron dev @liamzebedee got pretty close with Dappnet It would be great to close the gap between the Ethereum world and local-first.
26 Feb 2025
Someone needs to build Safe wallet software that runs locally, bundled with all necessary dependencies. Much easier to verify the integrity of local software
2
3
771
11 Feb 2025
#HBARSuiteV2 is coming very soon. SDK's will be available for Dev's to start building their own dAPPS within the #HBARSuite framework and start leveraging the Hashgraph the way it should be. Also, adding true decentralization utilizing multi-sig of multi-sig of multi-sig technology to take out the trust issue and have a fully decentralized dappnet to work with. Exciting times for sure.
1
3
11
368
one of the things I hope to see is a native ZK processor come out in the next 10yrs. dappnet always felt a bit tenuous, since the majority of frontends are centralized deeply throughout their backend (e.g. uniswap and its order engine) but a ZK processor could fix that
1
2
458
Replying to @DontTraceMeBruh
I guess the first step is to create a wallet and sync a node on the DAPPNET (you do that in the same desktop wallet, see the top left part of the login screen). The dappnet is a testnet that simulates the PoW part (but faster). It is meant to test smart contracts and DApps. Then, I think you should fork the "faucet" smart contract. For an airdrop, that seems to be the most appropriate. Note however that I believe some people made bots to drain the faucet. The BeamBots (a community project) did an airdrop DApp that was quite good, but to get your coins you needed to be the owner of an NFT from their collection. So it's not exactly your case here. Some examples of smart contracts ("shaders"), including the faucet, are here (see the readme too): github.com/BeamMW/beam/tree/… For any help, you can ask in the beamdevsupport chat in TG or the -dev-support channel in Discord. Some docs: beam.mw/docs/dev/using-beam-… And the older: beam.mw/docs/dev/using-beam-… Then, if you are going to write your own smart contracts, start here: github.com/BeamMW/beam/wiki github.com/BeamMW/shader-sdk… Regarding the front ends they are simple web apps (the wallet embeds Chromium 83 to run them). The frontends includes and interacts with the app.wasm file which is the wallet-side shader. @maxnflaxl, Did I miss something to help start with Beam smart contracts? Is there a simple frontend model or template that can be used? The faucet front end maybe?
1
5
85
18 Dec 2024
Still digesting the magnitude of the @nvidia @intel @hedera news but This blog post further reinforces my belief in native-layer maximalism. Verifiability and provenance is the foundation for what @EQTYLab, the product of Starling Labs which was the @Stanford @Reuters usecase with @CanonUSA on image provenance, is doing. They seem to be betting on confidential VMs with verification on ledger. Exactly what @HbarSuite is working on re: dAppNet architecture. More bearish than ever on EVM adoption. This cycle, the narrative is native-layer supremacy. community.intel.com/t5/Blogs…
4
24
146
5,664
11 Nov 2024
I want to talk to you at Devcon if you are interested in - Tevm - Light clients - AI daos - Dapp browsers (Mist browser dappnet etc.) - Sveltekit
4
3
22
2,181
6 Nov 2024
I know the utility of the network. I personally think that the atma usecase would have tremendously benefitted by dAppNet infrastructure like HBAR Suite to separate the business and on-chain logic while still providing the benefits of the public network. They get what they get. I'm sure a new enterprise use case is right around the corner. I'm more disappointed that the knuckle draggers pointed to Atma to justify the highest pay in the industry and it's just smoke and mirrors. We need to see them lean out.
2
2
19
383
17 Sep 2024
@HbarSuite: Tools for real-time, trustless collaboration over the internet. Join the #dAppNet revolution
17 Sep 2024
The experience our Team just had transferring out of the Multi-Sig Wallet on #HBARSuite was only what I can describe as eye opening.. speed, precision, ease of use, ... and speed. Test it.
2
19
501
12 Sep 2024
If you love the @HbarSuite smart node infrastructure but wish that they would go full degen with their revolutionary #DEX tech, you're going to love @SilkSwapDeFi. The coolest part about smart node applications is their modularity. While I'm sure we will see many #DeFi apps built on the tech, $SILK is going to have that first-mover advantage on $HBAR tokens and NFTs with future #dAppNet DEXs. And you don't even need to buy the token (pre-launch). Rn you will earn just for your participation.
SilkSwap is a community-driven platform powered by a dedicated group of HBARbarians committed to bringing decentralized finance to Hedera. With a focus on transparency and utilizing the cutting-edge technology of @HbarSuite, we are revolutionizing DeFi as you know it! #HBAR
5
40
1,160
19 Aug 2024
A thriving #DeFi ecosystem is comprised of many builders engaging community and providing services. THERE ARE NO "BUILDING BLOCKS" OF DEFI, ONLY TOOLS TO BUILD EASILY. Anyone who tells you otherwise is just trying to game TVL and rehypothecate assets. The @hedera $HBAR DeFi ecosystem will explode, but only when it is easy for builders to build on the network. Only one player is busting open that playing field--@HbarSuite. New tech is tough to explain in a way that works for everyone, so I hope you enjoy my latest attempt. Smart nodes are new way to build web3 applications with any programming language. Even applications and builders using smart contracts can add trust and decentralization above and beyond what is available to on-chain executables today. Smart contracts are secure and transparent--but the application that uses them may not be. Smart Nodes make web3 applications secure, verifiable, and tamper proof from end to end. YES--developers from every background will be able to plug their EXISTING applications into the Hedera network to leverage the advantages of web3. Take any application and leverage web3 where it makes sense (or not) for you--connect to HCS for trust, provenance, immutability, and aBFT enforcement of the rules--connect to HTS for low, fixed fees and frictionless transactions with maximum environmental efficiency--use smart contracts for transparency and on-chain functions, and/or keep your business logic private and off-chain without sacrificing trust through on-chain verification--leverage web3 decentralization to build internal redundancy and security, and/or use it to empower your participants with true ownership and meaningful participation. YES--applications built on smart nodes give developers an additional opportunity for monetization of their work. Creators can white label their applications for others to use without compromising their code or intellectual property. The more I think about it, the more I think this is single-handedly the killer app. It gives community developers a reason to build without the stress of launching their own project. YES--you can use smart contracts but why would you when you can build end-to-end trustless applications with no memory limits or language restrictions? I'm not saying "don't use the EVM" but start asking why. A good reason for this might be minting tokens--issuers of $wHBAR will soon be able to unify issuance under same contract upheld and maintained by a multi-signature threshold of issuers to eliminate counterparty risk and defragment liquidity in the ecosystem. What happens next is huge for web3--very few realize how unique this is in the space--and it's even bigger for the Hedera community. $HBAR and $HSUITE will be at the center of the new web3 development paradigm that actualizes Leemon's dAppNet vision and creates new ways to create trustless, immortal, and democratic on-chain applications. This is the grail.
5
18
66
3,066