BEAM

MimbleWimble 프로토콜 기반 국제 결제 플랫폼

home link https://beam.mw/

reference material

Community

Exchanges that listed the coin
5
Symbol
BEAM
Dapp
To be released
Project introduction

Mimblewimble 프로토콜을 기반으로 발생하는 거래의 완벽한 기밀을 보장하며, 블록체인 확장성을 결합하여 탄생한 기밀 암호화폐

사용자에게 편리함을 제공하고 Mimblewimble 위에 추가 기능을 개발하여 Mimblewimble 공간의 혁신을 주도하고 있습니다.

Executives and partners

Alexander Zaidelson

CEO

Wilke Trei

Board Director

Bo Dong

Board Director

Ferdous Bhai

Board Director

Amir Aaronson

COO

Coindesk

Forbes

Latest News

There is no news posted at the moment
Please leave a message of support for the team

go to leave a message

Medium

Beam: The Best in Privacy

TLDR; Following release 5.2 of Beam wallets, Beam will have achieved best in class privacy for all practical purposes and real-life applications. In this article we will review the key components of Beam privacy architecture summarizing over 30 months of hard work in both research and development. Looking forward, Beam is quickly becoming much more than just a privacy coin, with the addition of the Confidential DeFi platform and applications.The less they know the better you sleepAlex Romanov, Beam CTO, 2020A bit of HistoryThe Beam project started in March 2018 and after nine and a half months of development launched the first ever Mimblewimble based confidential cryptocurrency on January 3rd 2019, the ten year anniversary of Bitcoin Genesis block. During the next two years Beam has continued improving and expanding its technology and product line at an incredible speed. Some of the highlights include:Decentralized trustless Atomic Swaps between BEAM and BTC, LTC QTUM (and soon BSV, BCH, DOGE, DASH and Ethereum) blockchains.Chainwork SPV wallets — first ever implementation of the FlyClient protocol created by Benedikt BunzLaser Beam — instant confirmation direct payment channelsLelantusMW — first ever implementation of the Lelantus shielded pool based confidential protocol.BeamHash III — unique mining algorithm for smooth transition between GPU and ASIC mining.Confidential Assets — ability to create new confidential tokens on top of Beam blockchain.Beam has also created a vast ecosystem of beautiful and usable UI wallets for all platforms, both desktop and mobile, and accessible APIs for easy integrations. As of now, Beam is listed on over 50 exchanges and accepted in several hundred online stores and services.Now let’s see how Beam approached and solved the problem of creating the best privacy coin.Define PrivacyIn the context of a cryptocurrency privacy can be broken down into three basic questions:Who are you?What do you do?Who do you do it with?Let’s see how the Beam implementation addresses these questions one by one.Who are you?Bitcoin and many other cryptocurrencies have something called an ‘address’. If you want to send someone some coins you need to know their address. In Bitcoin, this address has two properties:1. It is used by the receiver of funds to prove ownership of the coins.2. It is recorded in the distributed immutable ledger (aka blockchain).Bitcoin addresses are pseudonymous, meaning that it does not contain the identity of its owner, however research has shown that it is very possible to establish this identity by tracing Bitcoin transactions to some point that has identity information attached to it (like an exchange with KYC data). And, due to property number 2, it is possible to do it retroactively by analyzing the blockchain backwards to the very first block and finding all transactions this address has ever participated in. Creating new addresses does not help since each such address has to receive funds from somewhere to be used, and these funds can be traced as well.The Mimblewimble protocol (MW), which Beam is based upon, does not have addresses. In basic MW transactions are created online and are signed by both the sender and the receiver (unlike Bitcoin where transactions are only signed by the sender). This means that no address or any other identity related information is ever recorded on chain at all.This does make the process of creating transactions much more cumbersome, which is why Beam has a Secure Bulletin Board System (SBBS) built into all wallets and nodes. SBBS is a decentralized and distributed encrypted messaging system that allows wallets to create transactions without having to be online at the exact same time and since it is built into all wallets greatly improves the usability of the process. To make it look even more familiar to Bitcoin users, SBBS has something called ‘SBBS address’ that is generated by the receiver and then used by the sender to start a new transaction. Unlike Bitcoin addresses, SBBS addresses have the following properties:1. It is NOT used by the receiver of funds to prove ownership2. It is NOT recorded in the blockchainHere is a short FAQ regarding SBBS messages:Is it possible to read all SBBS messages sent in the system?Of course, it is as simple as setting up a Beam node.Is it possible to know who is the sender of the message?Yes, with some work you can figure out the IP of the sender, and thus deduce their identity.Is it possible to know who is the receiver of the message or what it is about?No, the entire message is encrypted with the public key of the receiver and is pulled in by the receiver in bulk, so neither the identity nor the very fact of reception could be deduced.Does the fact of sending an SBBS message constitute a proof that a transaction has occurred?No, messages can remain unanswered, besides, there are many types of SBBS messages some of which are not related to transactions at all.In short, all you can know from the SBBS system is that some person has sent a message.What do you do?Even though there are no addresses in the blockchain, there is still SOME information there. What does it tell us about the value of the transaction or maybe any other properties?Short answer is: no identity or transaction information (amount, type, etc…) is visible on the blockchain.The value is encrypted. The type of the transaction is encrypted and when the transaction involves Beam Confidential Assets — new tokens that can be created on top of Beam blockchain and that inherit all privacy properties of Beam itself — even the type of asset is encrypted. Just by looking at a single transaction in a blockchain (see side note), the so called passive attack, you can only tell that some random looking inputs were transformed into some random looking outputs. This is where it gets interesting and brings us to the third question: Who do you do it with.Side note:Even looking at a single transaction in the Beam blockchain is not a simple task. When a node receives a new transaction from the wallet it does not immediately broadcast it to the network but rather engages the Dandelion protocol with decoy outputs. What it means is that the node rolls a dice (say a ten sided one like those you used when playing Dungeons and Dragons) and if a number between 1 and 9 comes out it selected a random peer and only sends the transaction to this one node (aka the stem phase of the dandelion), which in turn rolls its own dice and does the same. Only if a 10 comes out, does the node broadcast the transaction (aka the fluff phase of the dandelion).What’s more, if the node participating in the stem phase has some other transactions waiting, it non interactively merges them with the new transaction in a way that can not be separated back and if there are not enough transactions to merge with the node adds decoy outputs with zero sum that are indistinguishable from real outputs (these decoy outputs are later spent by the same node as decoy inputs and then removed by the MW cut-through feature, thus having zero total impact on the blockchain size). So the only way you can see a single transaction in Beam is if you are the first node in the Dandelion stem, if you are the one who sent it or if you are the one who sent all the other transactions in the stem. Possible, but not a simple thing to achieve, especially for the passive attacker.Who do you do it with?In the context of cryptocurrencies we can differentiate between two types of attackers.Passive attackers analyze information on the blockchain retroactively and do not send any transactions.Active attackers identify the targets wallet and attempts to deanonymize or link it to another person or wallet by actively sending transactions to that wallet and monitoring the blockchain state to determine the possible recipients of those funds.As we have seen the passive attacker has no chance against Beam. But who said the attacker should be passive?Let’s say an active attacker wants to establish a connection between two wallets, at least one of which is a known suspect. They will send transactions to this wallet (inputs of which are obviously known to the attackers) and then look at the blockchain to see which outputs were created. This process of determination which inputs were transformed to which outputs is known as reconstructing the transaction graph and as we have seen from the side note above it’s very difficult, but not impossible. Now, if the attackers are lucky, at some point one of these outputs along the way will be sent to an exchange, with the KYC information, which can be forced by law to disclose this information. Now the attackers have a non zero probability that these wallets are connected.This is of course, as they would say in the movies, ‘very thin’, but by repeating this active attack many times, and observing this correlation the probability could theoretically be increased to some statistically significant number that might imply a real link between the wallets.This attack on MW is known as the “MW linkability problem” and this is the only known attack against the MW protocol and is the only one used in articles that discuss MW weaknesses, exaggerating the simplicity of performing the steps described above.However, it is a valid point, so what do we do? Enter LelantusMW.Lelantus protocol was developed by a cryptographer Aram Jivanyan for the ZCoin cryptocurrency and adapted by Beam to augment the MW protocol. We called this adaptation LelantusMW and published a paper describing the changes we have done. The purpose of LelantusMW is to break coin linkability by burning the old coin and creating a new one which is completely unlinked from any previous history.LelantusMW creates a shielded pool, basically a pool of coins with a maximum anonymity set of 64K. Before we continue to describe how this helps us with the linkability problem let’s first understand what the **** an anonymity set is.What the **** is an anonymity set?Many cop movies feature a lineup, a process in which several individuals (usually five) are standing in one line and the witnesses are pointing at the one they recognize as the potential felon. Now imagine that you are standing in such a lineup but the other four people look EXACTLY like you. Since the witnesses have no chance to distinguish you from the others visually, they can only choose you by accident and the probability of this ‘accident’ is one in five. In this case we can say that this is an anonymity set of size 5.LelantusMW pool does the same trick with transaction outputs (TXOs) only with an anonymity set of 64K, basically like having 64 thousand people in that lineup. After TXO is submitted to the pool, a completely new output is created along with the proof that it corresponds to one of 64 thousand other outputs in the pool. This new output has never been seen before in the blockchain and is thus completely unlinked from the previous history. It looks as it has just appeared out of nowhere and it can not be traced back, thus breaking the transaction graph and solving the MW linkability problem.Side note: As a kind of added bonus, Lelantus is a non interactive protocol, which means that senders can submit coins into the pool for other wallets (receivers) without requiring their signature and thus emulate Bitcoin like transactions, the property which Beam has used in the recently released ‘Offline transactions’ feature in Beam wallets.Short FAQ regarding LelantusMW:If LelantusMW is so great, why don’t we use it all the time? Who needs MW anymore?Good question, however, nothing in this life comes completely free and Lelantus has some important tradeoffs to consider. The proofs needed for the process of extracting new coins from the pool are relatively large and more time consuming to construct compared to MW, and the Lelantus pool does not lend itself to the cut-through process, thus increases the blockchain size, which in turn is bad for decentralization. Which is why Beam has decided to go with the balanced combination of the two protocols to achieve the best tradeoff between privacy and scalability in terms of the blockchain size.One last question please, as a user, do I really need to worry about any of that when I use Beam wallets?Of course not. Beam wallets hide the complexity by providing three clear types of transactions:Regular — the good old MW transaction that should be used most of the time and costs minimal fees from 100 Groth. These transactions were available from the very first version of Beam wallet.Offline — that uses LelantusMW shielded pool and breaks the transaction graph but does not guarantee minimal anonymity set. These should be used when the receiver is offline and cost 0,01 Beam for each output. These transactions were introduced in the recently released 5.1 version.Max Privacy — that both breaks linkability and guarantees an anonymity set of 64K. They cost the same fee as the Offline transaction, but might take a significantly longer time to complete, depending on the anonymity set required. These transactions will be released with the next 5.2 version scheduled for October 2020.For any transaction type you choose, the wallet will automatically select the best set of available coins both in terms of privacy (as first priority), fees and change.To concludeBeam privacy architecture offers the combination of Mimblewimble, LelantusMW and Dandelion protocols to provide the best in class privacy with superior scalability and usability. All of the features described above are already deployed on Beam network starting from the 5.0 hard fork that was activated in July 2020, and are now being added to Beam Desktop and Mobile wallets, as well as APIs and the Beam blockchain explorer.Is Beam’s mission complete? Far from it. Even though Beam has achieved the best privacy, our next target is to expand this technology to more use cases including the Confidential DeFi platform and applications, such as Confidential Stable Coin, Decentralized Exchange for Confidential Assets, Non fungible tokens, and more. Check out our roadmap and follow the news for updates.Come discover Beam and join our community!Download Beam Android Wallet on Google PlayDownload Beam iOS Wallet on App StoreLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyContactAny feedback? Any question? Any concern or problem?Contact Team Beam:Telegram Support ChannelTelegram Community ChannelEmail SupportBeam: The Best in Privacy was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 10. 15

Eager Electron 5.1.9898  — ...

Eager Electron 5.1.9898 — Release NotesRelease Date: 1st OctoberTL;DR Release Highlights:This Eager Electron 5.1 release brings offline transactions, adding the option to use offline addresses: no need to wait for the receiver to come online anymore!Atomic swap fees have significantly reducedDozens of under-the-hood bug fixes you don’t want to know about, as Beam “just works”Desktop BEAM wallet welcomes the first external contributors: job done well by SomethingGettingWrong and sgaragagghu!Features:Enabled Offline transactions through the Lelantus MW protocol implemented at the last hard fork.For Offline transactions new “offline” addresses are supported: it includes all the necessary information for 10 payments so that a receiver doesn’t need to talk to the sender to create a transaction. Once the ten payments run out, the sender wallet will automatically request more payments from the receiver using SBBS. In case the Receiver is not online and not responding, the Sender wallet will show an indication that there are no more payments left and the user will request a new address using an external channel.Atomic swaps are significantly cheaper now due to SegWit support and a minimal fee rate is nicely recommended so that transactions will complete within a reasonable time.Confirmation count is implemented for CLI wallet and in the API to better align with exchanges.Improvements:Confidential Assets metadata is standardized. Read more here.Known limitations:Once generated, do not offer the same offline address to multiple senders of paymentsOffline transactions do not have payment proofs (to be added in version 5.2)Points to mention:Offline transaction fees are higher. The receiver pays his fee (per coin) when the coin is withdrawn from the shielded pool. To keep the anonymity set to the best value at any given time, the max privacy coins may remain in the shielded pool until the receiver decides to spend them. Hence, the withdrawal fee for each coin received via offline transaction can be paid when the receiver initiates the outgoing transaction of his own.For a more comprehensive list of the tasks accomplished please read hereVerifying release binariesPGP key: “A6C6 2C9F 5593 1860 AFF8 3BBB 997E AB9F 3DF7 F375”Go to https://keybase.io/beammw and get the Public PGP key.Download the signed binary file (with extension .asc) you want to verify.Verify the signature using PGP Suite or any other PGP verification toolsCome discover Beam and join the community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyEager Electron 5.1.9898  — Release Notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 10. 01

Eager Electron 5.1.9763 — T...

Eager Electron 5.1.9763 — Testnet — Release NotesRelease Date: 22nd SeptemberTL;DR Release Highlights:Offline transactions add the option to use offline addresses: no need to wait for the receiver to come online anymore!Atomic swap fees have significantly reducedDozens of under-the-hood bug fixes you don’t want to know about, as Beam “just works”Features:Enabled Offline transactions by implementing Lelantus MW protocolFor Offline transactions new “offline” addresses are supported: it includes all the necessary information for 10 payments so that a receiver doesn’t need to talk to the sender to create a transaction. Once the ten payments run out, the sender wallet will automatically request more payments from the receiver using SBBS. In case the Receiver is not online and not responding, the Sender wallet will show an indication that there are no more payments left and the user will request a new address using external channel.Atomic swaps are significantly cheaper now due to SegWit support and a minimal fee rate is nicely recommended so that transactions will complete within a reasonable timeConfirmation count is implemented for CLI wallet and in API to better align with exchangesImprovements:Confidential Assets metadata is standardized. Read more here.Fixes:CLI wallet: for Atomic Swaps with Electrum node — users can add any number of receiving and change addressesKnown limitations:When using active laser beam channels the CLI wallet should not be offline for over 24 hoursPoints to mention:Offline transaction fees are higher. The receiver pays his fee (per coin) when the coin is withdrawn from the shielded pool. To keep the anonymity set to the best value at any given time, the max privacy coins may remain in the shielded pool until the receiver decides to spend them. Hence, the withdrawal fee for each coin received via offline transaction can be paid when the receiver initiates the outgoing transaction of his own.For a more comprehensive list of the tasks accomplished please read hereCome discover Beam and join the community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyEager Electron 5.1.9763 — Testnet — Release Notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 09. 22

Beam Roadmap — the road to ...

Beam Roadmap — the road to Confidential DeFiOverviewFrom its launch on January 3rd 2019, Beam has released four major versions, each bringing a different set of features and improvements.The recent release of Eager Electron 5.0 marks the beginning of a new era in Beam development. What started as a best in class confidential and scalable cryptocurrency a little over two years ago, is now expanding to new an exciting path, a combination of both product and technology. We chose to call it Confidential DeFi and it will be an integral part of the Beam Roadmap for the next year or more. In this article we will outline the Roadmap, outlining the short and medium term releases, along with future research and development. We have discussed this both internally and with the community over the last weeks, and with the insights and feedback, are releasing the official update today.The roadmap can be roughly divided into three tracks: the Wallet track, the DeFi track and the Infrastructure track. On a timeline, it will span two major versions: Eager Electron 5.0, and Fierce Fermion 6.0, the next major version that will require a hard fork to introduce new capabilities into the Beam node.Confidential DeFi TrackThis section describes the Beam roadmap for Confidential DeFi infrastructure and applications. We plan to combine two different architectural approaches, Scriptless Scripts and Beam Contracts.Scriptless Scripts were introduced back in 2017 shortly after the invention of the Mimblewimble protocol and they describe an idea of replicating Smart Contract like functionality by running most of the calculation off chain and then validating the results using cryptographical concepts such as Schnorr Adaptor Signatures. Combined with Beams SBBS subsystem this will allow implementation of decentralized and confidential, multiparty trading applications, such as for example Perpetual Swaps described below.Beam Contracts technology is yet another amazing extension of Mimblewimble protocol for implementing Smart Contracts with built in scripting. It utilizes MW transaction kernels to consume input UTXOs while at the same time updating state variables inside the node. Those variables are then packed into Beam Contracts controlled by Beam Script (which is yet to be designed) thus allowing on chain calculations and emitting new UTXOs as their results.Scriptless Scripts and Beam Contracts together provide a powerful infrastructure able to support any existing DeFi application use case including Confidential Stable Coins, lending, and trading, all confidential and decentralized.Since most of the DeFi tasks require a lot of research and prototyping we will first release a series of POC and Testnet versions before deciding what is ready to be integrated into the mainnet wallets. Here is a breakdown of the planned milestones for Beam DeFi Track, roughly aligned with wallet release schedule.5.2 timeframe (September — December 2020)Beam Contract architecture POCFirst POC of the Beam Contract technology should include ability to create contracts with basic scripting capabilities and define clear APIs to use them. Most of this work is already in early design and research stages.Bridges to EthereumDespite providing a lot of value within the Beam chain, it is clear that having the ability to represent wrapped tokens from other networks would provide enormous benefits and possibilities for expansion and adoption. Ethereum as a leading DeFi platform today is clearly the top candidate for such integration. We can think of two possible architectures for Beam <> Eth bridges: federated and decentralized.In case of a federated bridge, issuance of the asset is controlled by a multisig wallet which should be trusted to monitor and balance amounts locked and distributed on each chain. This solution is relatively straightforward, however does require the trust in the federation that operates it.Decentralized bridges depend on the ability of all Beam nodes to monitor the state of specific contracts on Ethereum chain and are much more difficult to implement. One way to approach this is to create a two way SPV clients utilizing Beam Fly Client implementation to be able to get proofs from each chain.Already in 5.1 we are starting to research and implement the second, decentralized solution, which is expected to span the 5.2 timeframe.OraclesIn order to enable DeFi applications, we need to use oracles that provide reference price points for the traded assets. There are several possibilities to implement oracles either onchain to be used by Beam Contracts or using SBBS infrastructure to provide signed and verifiable information directly to wallets to be used in the process of negotiation and creating P2P trading contracts between the users. We are currently researching the possibility of building the oracles as well as integration with existing oracle providers.Perpetual swaps appOne of the first applications we are considering are Perpetual Swaps, which are a specific implementation of the futures contracts without a definite expiration date. The application will utilize SBBS for creating contracts and Laser Beam payment channels for locking collateral, handling funding transactions and settlement. More details on the implementation of the application will be provided in a future article.5.3 timeframe (December 2020 — January 2021)Wallet Track5.1 (July — August, 2020)Eager Electron major version has started with the release of the 5.0 and the subsequent hard fork on July 28th 2020 that has activated Lelantus MW and Confidential Asset support in Beam nodes. It also changed the mining algorithm to BeamHash III, the last of the two planned PoW updates that Beam has announced at launch. As usual, each major version is followed by several minor ones, each delivering a set of features and enhancements that do not require a consensus change.Work on the 5.1 version has started immediately after the release of 5.0. It is already in the testing phase and scheduled to be released in the upcoming weeks. This version includes several important features and improvements.Max privacyMax Privacy transactions utilize the new Lelantus MW infrastructure that was added in the recent hard fork and the related 5.0 version. Each such transaction contains two parts. First, the Sender submits UTXOs into the shielded pool with a max anonymity set of 64K. Then, Receiver extracts a completely new set of UTXOs that are completely unlinked from the previous history from the pool and can use it for further transactions. The time between these two parts is important as it allows for a sufficient number of other UTXOs to accumulate in the pool and provide the required anonymity set. Beam CLI wallets allow users to perform these operations separately for maximum control. In UI wallets, this operation is seamless and is built into standard Send and Receive operations.The specific window within which the anonymity set is maximal depends on the rate of Max Privacy transactions, the more they are used, the faster maximum anonymity is reached. This information is monitored and displayed by the wallet, so that at any time the user can know the exact anonymity set of each UTXO. The manual control, however, is not required since the wallet automatically selects the best UTXOs for each transaction, including the ability to send LelantusMW and Mimblewimble UTXOs in a single transaction.Offline paymentsSince Mimblewimble is inherently an interactive protocol, both the sender and the receiver need to participate in creation of the transaction. This introduces a very different user interface from what we are used to in other crypto currencies. However, using the LelantusMW technology, Beam has built an ability for senders to send funds non interactively even when the receiver is not online. We called this feature offline payments and it comes in two different flavors: using vouchers and using the offline address.First option, which will be released in 5.1, allows the user to embed a set of special keys called vouchers into an address created in the receive screen. By default, 20 vouchers are created. Since each voucher is about 100 symbols in length this number was chosen to allow the resulting address to be sent through most messengers without breaking into several messages. Each voucher is good for one transaction and when they expire, the wallet will either automatically request a new set from the receiver if it comes online, or prompt the user to ask for a new address with more tokens. The advantage of this, rather complicated, method is due to two properties. Each transaction uses a unique voucher, hence making it impossible to trace the user by trying to monitor which vouchers are used. Also, the sender can not track when funds that were sent using the voucher are spent, i.e extracted from the pool. Thus vouchers provide the maximum anonymity.The second option, that is currently planned for 5.2 version, uses a single ‘offline’ address, which allows to send any amount of offline transactions to the same address. Due to details of how LelantusMW pool works, there can only be a very limited (and definitely capped) number of such addresses created for each wallet since each new address would require the wallet to rescan the pool for UTXOs sent to it. This option is less secure since it allows deanonymization by comparing offline addresses sent out to different senders and also the sender can see when the funds are extracted from the pool. It is however much simpler for the user and more consistent with how most other crypto currencies work, which is why we recommend it for specific user cases like donations and non-interactive pool payouts, rather than general confidential transactions.Atomic Swap improvementsAtomic Swaps are a great and completely confidential decentralized way to securely exchange Beams for BTC, LTC and QTUM without any third party. In this version this feature becomes even better with replacing intermediate outputs and inputs with SegWit, lowering the fees for the swap significantly. We also provide optimal fee rate recommendations directly from the respective blockchains thus removing the necessity to obtain them manually.Redesigned settingsAs more features are added into the wallet the settings page gets more crowded, so we have decided to redesign it and create logical groups to simplify finding and accessing the relevant settings.5.2 (September — November, 2020)Beam Vault and Secure SyncBeam SBBS is a great decentralized encrypted messaging system that allows wallet to interactively create MW transactions. It is however limited by design to only hold the message for 12 hours after which the message will expire and is no longer available for the recipients. Beam Vault is a centralized but trustless service that can store SBBS messages for longer periods of time. It can also be used to synchronize Beam Wallet that uses the same seed across multiple devices, something that was previously problematic and hence discouraged. As SBBS will gain more function with addition of DeFi functionality this service will be even more useful as a complementary and backup option for the SBBS system.Address Book improvementThe Address Book feature is not new. It appeared in all wallet versions from the very beginning. It was, however, hardly used as most transactions used ad hoc SBBS addresses and hence writing them down was irrelevant. In few cases where permanent addresses were used, they are usually related to either exchanges or pools. However, with the addition of offline payments and Confidential Assets, the address book takes on new roles and needs to be improved and updated.Trezor T supportWe are planning to roll out a custom firmware for Trezor T that supports Beam with integration into Beam Desktop Wallet. Ledger X development is more difficult and still in progress.Swaps with BSV, BCH, Dash and moreMore coins will be added to our Atomic Swap support, mostly BTC forks. These will include BCH, DASH and BSV. We are also looking at RVN and probably a few others.Beam Blockchain Explorer improvementsFollowing the introduction of new features we need to reflect their state in the blockchain explorer and related APIs. These should include statistics for Atomic Swaps offered and accepted, The current state of the LelantusMW pool including estimated hold duration for achieving maximum anonymity set.Wallet UI for Confidential AssetsBeam UI Wallets should be able to transact using any existing Confidential Asset, in addition to native Beam coins. Since CAs inherit all properties of Beam coins, it is possible to seamlessly mix different asset types within the same transaction. The challenge is to integrate this functionality into Beam UI in a way that would not negatively impact its usability, while still being able to support all relevant use cases for power users.Beam Web Wallet and Wallet Service Mainnet releaseWe have recently released the Testnet version of Beam Web Wallet and Wallet Service, which is a centralized but trustless backend component able to relay SBBS messages and handle the connectivity layer for multiple wallet processes. Both components still require a lot of work to be ready for production including extensive security and stability testing, which is why their release is most likely to take place towards the end of the 5.2 time frame.Infrastructure Track5.1 (July — September, 2020)GhostDAGGhostDAG is a novel consensus algorithm that replaces the blockchain with a k branching directed acyclic graph, which means that at any time there can be between one and k valid branches. This means that blocks can be created faster resulting in higher network throughput. It also provides better miner decentralization and reward distribution as more blocks are created.Side chains POCAs we move forward it becomes clear that not all of the features could be natively supported on the mainnet while at the same time maintaining its stability and integrity. However, we also do not want to ever stop innovating and taking Beam and its underlying protocols to new extremes. The way to combine these two opposing desires is by introducing side chains.Beam Side Chain, is basically another independent Beam chain with few key differences and modifications that would make it incompatible with the main chain. Such modifications may include for example as different consensus mechanisms such as GhostDAG or Proof of Stake, or even addition of Smart Contracts. Despite being a separate blockchain, side chains are designed to maintain two side peg to Beam at all times, making it possible to reliably move value from Beam Mainnet to Side chain and back.Depending on their purpose, side chains can be either created empty or use their own native token. In the first case it and only uses token moved from the Beam main chain. Instead if it uses a native token, it can be either co-mined or emitted independently using a separate mining algorithm. In any case, new assets created directly on the side chain could never be moved onto Beam and interfere with it’s consistency. They can, however, be exchanged for Beam or any other Confidential Asset on Beam network using Atomic Swaps.Fierce Fermion 6.x EraNext major version will come with a fork that will not change the PoW algorithm but rather introduce crucial consensus breaking features to support Confidential DeFi infrastructure.Additional topicsThe following is a list of topics that were raised but not prioritisedAtomic Swaps with EthMultisig wallets requiring several signatures to sign the transactionAudit wallet Audit system that can monitor multiple walletsTOR/i2p integrationMixnet IntegrationSBBS over dandelion Add Dandelion protocol to SBBS messagesBeam Roadmap — the road to Confidential DeFi was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 09. 17

Beam Community Call

The time has come for Beam’s 1st community call!With some huge steps being taken on the development and product fronts, and a big shift of focus towards confidential DeFi coming with the latest Hardfork, what better time for Beam’s 1st Community Call.The community has always been at the heart of Beam, and it is with your support that we continue to grow and push forward together.The Agenda:The call will be be broken into three parts:5.2 Kickoff: To get things rolling Beam Tech Lead, Alex Romanov, will take us through the intricacies of the upcoming Eager Electron 5.2 developments, present the list of features that are being considered, and seek community opinion on what to prioritise.DeFi Architecture: Alex will then walk us through the Beam DeFi architecture, what it means, how it will be possible, and what opportunities it creates. It will be a great chance to get more familiar with what is being built out, and what it means for us as a community.Q&A: This is where you step in!! Much of what Beam entails includes the great suggestions and feedback from the beloved Beam community. Here we will be able to ask questions, and give any feedback or suggestions on the upcoming developments, confidential DeFi rollout and Beam in general.Come prepared with your toughest questions and most meticulous feedback!Save the DateDate: 12th of August, 2020Time: 10:00 AM, Eastern TimeLocation: TBA closer to the date - the event will be a live video callSee you there!It’s with great pleasure that the first Beam community call will take place, and we are looking forward to seeing you all there.Confidentially yours,Team BeamCome discover Beam and join our community!Download Beam Android Wallet on Google PlayDownload Beam iOS Wallet on App StoreLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyBeam Community Call was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 08. 05

Beam Web Wallet 1.0.0 — Tes...

Beam Web Wallet 1.0.0 — Testnet — Release NotesRelease Date: 5th August 2020This is the initial version of two complementary products:Beam Web wallet (released as a Chrome extension) — to make Beam more accessibleNon-custodial wallet service — to enable 3rd-party integrationsGeneral info:Privacy first: you, and no one else is the seed phrase keeperThe release is compatible with Eager Electron 5.1 products that are currently being developedFeatures:Both full-screen and extension mini views to see your balance, transaction status and historySend and receive Testnet Beam coins using transaction tokensObserve the status of your transactions in real-timeView the list of available, locked and spent coins in the UTXO (unspent transaction outputs) screenThe sender can create and verify the proof of transactionIntegration with community faucet to receive BEAM and try the wallet right after the installationPrivacy mode, well-known in Beam mobile wallets: tap the little eye icon and make the balances “disappear” till you’ll toggle the icon againPoints to mention:Transaction tokens replace SBBS addresses from 5.1: these tokens look like longer addresses and also include additional information such as requested amount, currency type, transaction type etc.Known limitations:The restore from seed phrase is yet to be implemented (it’s a Testnet release and you can always get more Beam from the community faucet)Only single-use tokens are supported: once issued, the token will remain active for 12 hours.Link for downloading from the web store: https://chrome.google.com/webstore/detail/beam-web-wallet-testnet/ilhaljfiglknggcoegeknjghdgampffk?utm_source=chrome-ntp-iconCome discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyBeam Web Wallet 1.0.0 — Testnet — Release Notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 08. 05

Beam Confidential DeFi Plat...

IntroductionWith the release of Eager Electron 5.0 version, Beam has mostly completed the set of infrastructure features making it the best confidential cryptocurrency in the world today. However, the Beam story is just getting started since the confidential transfer of value is just one of the many possible applications of Beam technology. In this article, we will outline the applications that will be developed on top of Beam platform during the second half of 2020 and throughout 2021.We are building a platform that will allow developers to create confidential decentralized financial applications, using the building blocks described in this article, together with a variety of tools and APIs we will provide for this purpose.ConceptsBefore we dive into specific application types, we would like to provide an overview of several key concepts pertaining to our case in order to build common ground and avoid misunderstandings.Decentralization: Centralized vs Decentralized vs FederatedThroughout the article, we will often mention terms like Centralized, Decentralized or Federated, and we would like to explain what is meant by each one to avoid confusion and many of the common misunderstandings. Centralized refers to a system, application, or asset controlled by one legal body. Federated means that control is spread over several bodies, a number of which is still small in comparison to the overall network size, say, the total amount of nodes or block producers. These bodies are assumed to be uncorrelated and have an efficient way of reaching consensus assuming some majority of them are honest. Federated bodies are almost universally ‘permissioned’ — meaning an agreement of the current members is required to join the Federation. In contrast, Decentralized systems are almost by definition ‘permissionless’ and are controlled by a relatively large and dynamic number of uncorrelated bodies, with no central authority.In the context of DeFi, it is obvious that any representation of any real-world (i.e non-crypto) asset, can only be either centralized or federated. In fact, as of today, this is also true to many of the crypto assets as well, since contracts are in most cases controlled by a single entity, and often preserve some centralized control. The exact scope of this control might differ in each particular case and is supposed to be as minimal as possible through the process called ‘trust minimization’.Wrapped Assets vs Cash Settled contractsIn the context of this article, wrapped assets represent asset classes that hold some actual amount of the underlying asset as collateral. Thus, for example, wBTC on Beam assumes there are some actual Bitcoins being kept somewhere and could be exchanged back and forth for their wBTC counterparts. For technical reasons on the Bitcoin side, the BTC lock can only be done in either a centralized or federated way, with some additional ‘trust minimization’ components.Cash settled applications provide a representation of different asset types using centralized or federated oracles, but do not hold the actual asset itself. In this case, users can either trade contracts, such as CFDs (Contract for Differences) or cash-settled futures without the underlying asset changing hands.Types of DeFi applicationsAs of today, DeFi applications mostly fall into three major categories: Lending, Synthetics and Decentralized Trading.LendingLending is a broad category which includes various types of lending / borrowing as well as margin trading, liquidity mining and similar applications. In most cases the lenders would get dividends on the liquidity they provide to the market. The borrowers, on the other hand, will be able to use more funds to leverage their positions, either short or long in the provided currencies.SyntheticsSynthetics generally mean the ability to represent different types of real-world assets using on-chain tokens. Such assets may range from stocks and commodities to various types of non-fungible asset classes such as real estate or other types of property. On the Beam chain, each asset is represented by a matching Confidential Asset type or CA for short (described in more detail below) and their relation to the real-world assets is handled using the Oracles.One specific application of a synthetic asset are stable coins that are tied to a real-world currency, usually the US dollar. On Beam, this can be implemented either algorithmically by using collateralization, in a way similar to how Dai works or by moving over existing stable coins using custodial Bridges. Stable coins have gained a lot popularity recently and are used in a lot of financial applications.Decentralized Exchange (DEX)Both lending and synthetics are often used to execute a wide variety of trading contracts such as futures, options, long and short trading and a multitude of other financial instruments including many variations of derivatives. Decentralized Exchange (or DEX for short) is a platform that allows the execution of the above-mentioned contracts. Unlike centralized exchanges, the goal of DEX is allowing users to keep custody of the assets whenever possible and use trust minimized federated schemes in case it is not.Amongst the different types of trades that can be supported by such exchanges are; taking long and short positions on various assets, Contracts For Difference (CFDs) and Perpetual Swaps, which are variations on the futures contracts without the predefined settlement date.How does it work on Beam and what makes Beam different?In this part, we will provide an overview of Beam DeFi infrastructure including the high-level building blocks we will provide to enable applications that were described in the previous section.Beam Confidential AssetsConfidential Assets (aka CAs) were introduced in the recent EE 5.0 release. Any Beam user can now create a new asset type by locking 3000 Beam, thus becoming the *asset owner*. The owner can then emit or burn any amount of the newly created asset that belongs to that owner, an event which is openly visible on the blockchain and reflected in the blockchain explorer. If the owner controls all of the emitted asset, he/she can choose to burn all of it and unregister the asset type, thus getting back the locked deposit. Of course, if some amount of the new CA was transferred to other users, it can no longer be burned and thus it is no longer possible to unregister the CA for obvious reasons. The CAs inherit all the confidentiality and scalability properties of the original Beam coin, and are handled by Beam wallets. It should be noted that while individual transactions and holdings are fully confidential, the total supply of a CA can be seen on the blockchain.OraclesOracles are an essential part of connecting blockchain applications to real- world events and financial data. Oracles are always either centralized or federated, at the moment no truly decentralized oracle architecture exists. This is not a major issue for most applications. Oracles serve as final arbiters on the contract settlements.Scriptless ContractsCurrently the most popular way to implement DeFi applications is by running deterministic scripts called Smart Contracts on all nodes in the system and updating system state according to the results of their execution. These scripts are usually written in a special language that can be interpreted by the virtual machine built into each node. Furthermore, blockchains implementing Smart Contracts usually use account based models. How would it be possible to build such applications on Beam which does not have Smart Contracts and is UTXO based?By now we thought we would get used to the magical properties of the Mimblewimble. We already saw it with Cut Through, Atomic Swaps, Laser Beam and Lelantus and this time it will allow us to build ‘Scriptless Contracts’ that would both allow transition between UTXO and Account model, and implement complex business logic. The secret, as usual, lies in the implementation of the transaction kernels, key enablers of the Mimblewimble extensibility. Just as in Lelantus, the kernels enable the transformation of UTXOs into system state and vice versa thus allowing contracts to operate.The other part of the application logic takes place off-chain and is performed via exchange of SBBS messages between the wallets and creation of new types of transactions. The basic idea is that while the trade itself is formed off-chain in the form of a multisig agreement, the settlement and verification are done on-chain, thus making sure the eventual state of the system is always consistent.The resulting architecture thus utilizes all of the Beam infrastructure including Atomic Swaps for locking non-Beam collateral, Laser Beam channels for instant payments where required, SBBS for all off-chain negotiations and ‘Scriptless Contracts’ to handle the application logic.SidechainsBut what if you absolutely must have Smart Contracts? Or you want to use PoS consensus? Or both? Of course, it would not be possible to do that on Beam Mainnet without having to deal with a multitude of consequences. It would be, however, possible to launch a Beam sidechain in which these changes could be implemented and move assets seamlessly from Beam to the sidechain and back again using Beam chain interoperability contracts.If a sidechain does not have a native token, any confidential asset, including Beam itself, can be locked on the original Beam chain and then reissued on the sidechain for the same owner. The moving back works in a similar way, the asset is burned on the sidechain and then unlocked on Beam Mainnet. The combination of the above allows to seamlessly channel trades between chains. If a sidechain has its own token, this token can not be moved to Beam, it can only be used within the side chain.If the sidechain does have a native token, it can not be moved to the main chain, but the assets from the main chain can still be moved and traded on the sidechain against either other assets or the native token. Since both chains support the Mimblewimble protocol the trading will be seamless and provide the same properties of confidentiality and scalability as the Beam chain itself.BridgesBridges are mechanisms that allow locking coins on foreign chains such as Bitcoin or Ethereum, and receiving their equivalent representation as Beam CA. Bridges can be either centralized or federated, with some trust minimization in case the original chain supports smart contracts.The road to Confidential DeFiBeam was always known for its innovation, speed of execution and attention to user experience. Beam Confidential DeFi will continue these traditions taking Beam to the next level and bringing usable confidentiality to the DeFi world.Based on the building blocks we described above, the community will be able to build any number of DeFi applications with diverse functionality that will fulfill the growing need for confidential DeFi services. This year, we are seeing an unprecedented growth and interest in DeFi applications, and the trend will continue into the future. As a platform, Beam is offering all the DeFi capabilities, plus (and it’s a very important plus) full confidentiality of people’s operations and assets. The future of DeFi is confidential and Beam has what it takes to build that future.Of course, there will be many technological and cryptographic challenges along the way, but the journey is looking amazing and worthwhile. In our next roadmap update we will lay out the essential milestones for the rest of this year and into 2021. In Beam, no matter how far we go, it always seems the best part is still to come.Come discover Beam and join our community!Download Beam Android Wallet on Google PlayDownload Beam iOS Wallet on App StoreLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyContactAny feedback? Any question? Any concern or problem?Contact Team Beam:Telegram Support ChannelTelegram Community ChannelEmail SupportBeam Confidential DeFi Platform was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 07. 23

Beam Mitigating Reorgs

This note is to advise and reassure our community that Beam Team is dedicated to keeping our decentralised network safe from attack.Download Beam Android Wallet | Beam iOS Wallet | Beam Desktop WalletMitigating Double-Spend AttacksBefore the recent consensus change in Beam, where we moved from BeamHashII to BeamHashIII, we made attempt to reach out to exchanges and pools to help us mitigate any chance of irregular activity with the Beam blockchain. Specifically, to help us combat any unseen attack on the network where a miner might hold more than 50% of the network hashrate. We ensured that the majority of exchanges implemented longer confirmation times for deposits of Beam, and we also introduced a 60-block rolling checkpoint, a mechanism that prevents reorgs deeper than 60 blocks. Unfortunately, there were a minimal number of exchanges who did not acknowledge the request to extend confirmation times.Important request to exchanges and OTC handlers: Please allow at least 70 block confirmations before accepting user funds.So, over the past short while, we have noticed some irregular network activity and as a result feel it only right to issue this statement.Below is the timeline of known attacks, and the steps we took to mitigate them.27–05–2020EventsSeveral big reorgs happened in a row.730833 -> 730779 -> 730873 (-54, +94)730938 -> 730902 -> 731048 (-36, +146)731075 -> 731066 -> 731116 (-9, +50)Investigation:We had 16 public mainnet nodes, from which we collected and analyzed their logs to see the whole picture. Mainly to understand better, if it was perhaps a deliberate attack, or if reorgs of the chain happened spontaneously.In this instance, the logs didn’t show a consistent picture. We saw considerable deviations in the state of our nodes due to poor inter-node connectivity. Different nodes followed different branches for significant duration, whilst irregular, sporadic reorgs happened.Our conclusions:Poor network connectivity, spontaneous (natural) network splits couldn’t be ruled-out, and this could be a logical explanation to reorgs.Attack was possible, but not confirmed.Our actions:We took measures to reinforce inter-node connectivity.Fixed some issues in dynamic peer managementAdded possibility to configure permanent peers, i.e. peers to which the node should maintain connection constantlyUpdated all our mainnet nodes, configured them to maintain permanent connection to each other, to have a super-connected cluster.Advised all known pools and exchanges to do the same11–06–2020Events2 big reorgs happened in a row.753811 -> 753796 -> 753815 (-15, +19)753904 -> 753821 -> 753927 (-83, +106)Investigation:We collected and analyzed logs from all our 16 mainnet nodes. This time they showed a perfectly consistent picture; all were in tight sync, and each underwent exactly the same reorgs at the same time. So this rules-out network connectivity problem.So, it seemed that a very powerful miner mined for some period of time in isolation. But the question still remained: was this a deliberate attack, or maybe the most powerful mining pool just lost the connection temporarily?We analyzed the reorged blocks and noticed that they were mostly empty, but some one of them contained a single transaction. This was consistent with how an attack might be played out. In isolation there should be no transactions, the user can only send funds to themselves (in MW, transactions are built mutually). Sending funds to yourself — looks like a deliberate double-spend. In addition we noticed anomalies in the network hashrate. For the duration of the (alleged) attack the hashrate of the honest community dropped considerably, but the (alleged) attacker hashrate was significantly higher than this drop. Which means; if we estimate the total hashrate of the network — it increased dramatically.We discovered that during this time there were abnormally big hashpower orders on NiceHash.Our conclusions:Double-spend attack is very likely.Complexity of the attack: modestTemporary isolation can be achieved by tweaking the firewall.No need to know or modify our codeCost of the attackGiven the current Beam prices and mining difficulty it’s feasible.If the attack is successful — the attacker also gets the blocks rewards, which further reduces the costOur actions:We implemented a rolling checkpoint mechanism that prevents automatic reorg any deeper than 60 blocks.Instructed all pools and exchanges to have at least 80 confirmations for depositsWe realized that our change to the consensus rule can lead to a network split, so we also did the following:Added network split detection and alert mechanismsAbility for the user to reorg manuallyAutomatic reorg to arbitrary depth in case the current branch is abandoned. This is to make things easier for ordinary users. In case of network split, once the attack is over, their nodes will reorg automatically after some time.15–07–2020Events4 big reorgs occurred within several hours during the night. 2 more reorgs during the next day. 2 reorgs on the next evening and night.800823 -> 800788 -> 800833 (-35, +45)800923 -> 800913 -> 800938 (-10, +25)800979 -> 800958 -> 800991 (-21, +33)801014 -> 800994 -> 801021 (-20, +27)802281 -> 802240 -> 802290 (-41, +50)802341 -> 802321 -> 802351 (-20, +30)803422 -> 803366 -> 803431 (-58, +65)Investigation:All reorgs follow the same pattern we observed previously. Reorged blocks are mostly empty, with only few transactions (that look like double-spend).Same fluctuations of hashrate.None of the reorg was above 60 blocks, as expected.No Network splitThis time we further analyzed the reorged blocks where we suspected that there had been a double-spend contained within them. This showed that the replacement block spends some input that was spent also in the original block, whereas the outputs of the replacement block are different. Meaning, the original block contained A->B, whereas the replacement block contained A->C.Unfortunately we couldn’t perform the same analysis on previous reorgs, because our nodes didn’t keep reorged (orphaned) blocks forever. However we could do this for the most recent reorgs. And this is what we discovered.803422 -> 803366 -> 803431H=803424 Double-spend. Original Height=803375802341 -> 802321 -> 802351H=802330 Double-spend. Original Height=802329802281 -> 802240 -> 802290H=802250 Double-spend. Original Height=802246So for the last 3 reorgs we are CERTAIN. This is a double-spend. We also know the exact spend height of the original (reverted) transaction. What remained unclear is WHY the attacker keeps doing this? Reorgs no deeper than 60 blocks should not cause funds to be lost on exchanges, because they should have at least 80 confirmations. Later in the evening we discovered abnormal trading values on some known exchanges and discovered that, contrary to our advice, they have had a small number of confirmations for Beam deposits.Our conclusions:The attacker had identified exchanges with a small number of confirmations, and was able to conduct the attack repeatedly. Unfortunately exchanges didn’t notice this in time, despite our best prior advice, and their loss of funds.It is likely that the attacker also tried to conduct the attack on other exchanges, but didn’t succeedSome other exchanges which we contacted in this matter, reported they had deposits on the corresponding heights, but were reverted. Luckily they had took our advices and enabled enough number of confirmations for deposits of Beam.The attacker might also have tried deeper reorgs (to attack other exchanges), but didn’t succeed.In addition to stealing funds from exchanges, attacker puts the network at riskSome dependent transactions may not be recovered after the reorg, causing inconvenience to usersRisk of network split is imposedOur actions:We urgently contacted the affected exchanges we found, and asked them to raise the number of confirmations.We’re working on our API for pools and exchanges, so that their wallet will select only “mature” UTXOs for transactions, to prevent “accidental” transactions failure due to reversal of ancestor transactions. To reduce possible side effects of the reorgs.This has been a very thorough and in-depth investigation by our team to pinpoint and mitigate against these attacks and it is not a unique event to Beam. It is a possible scenario for any cryptocurrency.In the analysis of the events, we would like to assure and thank our community for your patience and understanding during this time of duress.Finally we would like miners to consider how best you can assist us whilst we monitor and mitigate these attack events. Join smaller pools, bolster your decentralised Beam network by spreading your hashrate, protect your mined rewards from reorgs and don’t let these attackers perpetuate on overweight pools. Don’t enable them by centralising onto the largest pools.Come discover Beam and join our community!Download Beam Android Wallet on Google PlayDownload Beam iOS Wallet on App StoreLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyBeam Mitigating Reorgs was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 07. 17

A Guide to Creating Confide...

Beam has released the highly anticipated Eager Electron set of products, and with v5.0 at block height 777,777 came the capability to create Confidential Assets directly on the Beam Privacy blockchain. This guide will assist you to use the functions and create your own first confidential asset with Beam.To note, the following guide shows how to create a Confidential Asset connected to a local node on your own computer, although it is also possible to create a CA by connecting to any remote node.A list of nodes can be found on page https://beam.mw/downloads/ and to use a remote node, simply replace 127.0.0.1:10127 in the configurations below to point at the closest remote node to you.REQUIREMENTSYou will need — 3000 Beams, which will be locked, to enable the creation of the Confidential Asset.IMPORTANT NOTE: To retrieve these 3000 Beam, you will need to burn the entire number of the asset.When you intend to distribute your own CA, you will not be able to retrieve these locked Beams without personally owning every single CA amount that you have issued.Please be aware that the creation of a Confidential Asset is an important decision and it is recommended to try on Testnet first, as assets are immutable — TESTNET GUIDE HEREWhat is a Confidential Asset?A CA on the Beam blockchain is a fully private asset, issued by you.What can a Confidential Asset be used for?CA’s can act as many things like loyalty points for your customers, individual tradable company shares and even confidential synthetics / digital assets like bonds or collateral-backed stable currencies. Use cases for CA’s are truly endless.So let’s begin creating your first confidential asset on the Beam blockchain…NOTE: This guide utilises the MAINNET of Beam, and any CA’s you create using this guide will LOCK the 3000 Beams you used to create it. That’s clear? then let’s continue…WHAT YOU WILL NEEDBEAM-NODELocal CLI (Command-Line-Interface) Node for your computer to allow your Beam Wallet to read the Blockchain and stay synchronised.https://beam.mw/downloadsClick the link to ‘Node’and download to your computer.BEAM-WALLETLocal CLI (Command-Line-Instruction) Wallet for your computer to allow you to store your own immutable currency.https://beam.mw/downloads/Click the link to ‘CLI Wallet’and download to your computer.After NODE and WALLET are unzipped and on your computer, follow the steps below to get started.Step 1 — beam-node.cfgUsing a simple text editor, add three lines into beam-node.cfg file and save it;port=10127peer=node01.mainnet.beam.mw:8100,eu-node02.mainnet.beam.mw:8100,eu-node03.mainnet.beam.mw:8100,eu-node04.mainnet.beam.mw:8100,us-node01.mainnet.beam.mw:8100,us-node02.mainnet.beam.mw:8100,us-node03.mainnet.beam.mw:8100peers_persistent=1Step 2 — Synchronise the NODEOpen a terminal window (CMD on windows) and use the command:./beam-nodeAllow the node process to reach 100% synchronisation, as shown below (leave this window open and the process running):Step 3 — Initiate the WALLETWhilst leaving the node window open and running the node process, open a second terminal window and enter the command:./beam-wallet initThis will give you a new wallet, complete with 12 word seed phrase and an initial wallet address. Copy the seed phrase and store it somewhere safe. In that same window, now run the listener command to keep your wallet hearing the blockchain height from the node (leave the listening window open and the process running):./beam-wallet listen -n 127.0.0.1:10127Step 4 — Register your CATo create a confidential asset on the Beam blockchain, you will require you to have 3000 Beams (+tx fee) in your wallet../beam-wallet asset_reg --pass yourwalletpassword -n 127.0.0.1:10127 --asset_meta "STD:SCH_VER=1;N=CANameCoin;SN=CATicker;UN=CAFullName;NTHUN=CASingleUnitName" --fee 100 --enable_assetsLet’s break this command down a bit to understand it easier…asset_reg = register the asset on the Beam blockchain--pass = the wallet password your wallet was created with in step 2-n = specify the node to listen on (can be 127.0.0.1:yournodeport or a remote node like pool.raskul.com:10127)--asset_meta : STD = prefix, denotes that the metadata is standard formatSCH_VER = metadata schema version — currently must be 1 N = Give your Confidential Asset a unique name (eg Bitcoin)SN = The shortened (or TICKER) name for your Confidential Asset (eg BTC)UN = Full user-determined name for your Confidential Asset (eg Bitcoin)NTHUN = Smallest denominational value of the Confidential Asset (eg Satoshi)--fee = the fee to pay (in Beam) to register the Confidential Asset--enable_assets = The flag to command the wallet to enable Confidential Assets (reused in every CA command line)There are also extra metadata options which provide a variety of functions including a way to add a favicon and a logo to your CA. Please see https://github.com/BeamMW/beam/wiki/Asset-Descriptor-v1.0 for more information.The Beam wallet will then administer an ASSET ID, make a note of this. An example of the Wallet output is shown below. You can see in this example an Asset was created with Asset ID 1.Your wallet will then perform interact with the Beam blockchain to create the asset you have specified.MINIMAL INFO OF THIS IS SHOWN ON THE BEAM BLOCKCHAIN — CLICK HERE TO SEE THISSee below the only public info which is shown, is the Asset ID and it’s unique ASSET CREATION HASH.Step 5 — Issue amount of CAAfter registering the asset, now it’s time to determine how many you want to issue in the first instance (you can add more to the amount at any time)../beam-wallet issue --pass yourwalletpassword --asset_id 1 -n 127.0.0.1:10127 --amount AmountOfCAToCreate --fee 100 --enable_assetsYour wallet will then perform the processes and conversations with the Beam blockchain to issue the number of assets you have specified. In this case I have created 10127400000 ‘TICO COIN’.MINIMAL INFO OF THIS IS SHOWN ON THE BEAM BLOCKCHAIN — CLICK HERE TO SEE THISSee below the only public info which is shown, is the Asset ID and it’s numerical issuance. If in the future you were to issue further amounts of the same asset, this would also be shown in the blockchain — and the value of extra issued assets. This ensures that no infinite number of any one asset can be created without it being publicly known, and thus mitigating hidden inflation.The asset will now be locked for 24 hours before you can use it, send it or burn it.A MORE FULL GUIDE TO ALL OF THIS CAN BE FOUND IN THE EVER-CLEARLY EXPLAINED BEAM DOCUMENTATIONS ONLINE HEREExtra — Burning the CA to receive your 3000 backIt is possible to obtain refund of your locked 3000 Beams, by burning the entire asset emission and unregistering the CA. The steps below show how this is done and will take at least a 48hr period to complete this process and have your locked Beams refund.NOTE: To enable refund of the locked 3000 Beam — you MUST BURN EVERY SINGLE CA TOKEN (which means if you have sent even 0.00000001 of a CA to anyone, your 3000 Beams are not returnable until such time that your ASSET EMISSION is 0)First you need to burn every token you have created — to do this we use the command CONSUME. Make sure you enter the EXACT amount of asset to burn int he command line by using the –amount (n) flag./beam-wallet consume --amount 1 --pass yourwalletpassword -n 127.0.0.1:10127 --asset_id 1 --fee 100 --enable_assetsAfter burning the CA, there is again a 24hr “Max Rollback” period to wait until you can unregister the CA and have your Beams refunded. Why the need to wait? The Beam node assigns an asset ID during the asset registration process and uses the first ID available.Technically there can be a situation when one asset is unregistered, asset ID becomes available and the next registered asset takes the id that has been previously used. The 24hr lock period is introduced to ensure that asset receiver would never receive an unexpected (forged) asset and making sure that every CA is totally unique to it’s owner.So after the 24hr period since burning the asset, you may now unregister the asset and receive your 3000 Beams back to the wallet which created the asset. Use the following command;./beam-wallet asset_unreg --pass yourwalletpassword -n 127.0.0.1:10127 --asset_id 1 --fee 100 --enable_assetsYour locked 3000 Beams will then show up in your wallet.This guide can also be found at https://www.raskul.com/creating-a-confidential-asset-on-beam/ContactAny feedback, questions, concerns or problems?Contact Team Beam:Telegram Support ChannelTelegram Community ChannelEmail SupportCome discover Beam and join our community!Download Beam Android Wallet on Google PlayDownload Beam iOS Wallet on App StoreLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyA Guide to Creating Confidential Assets on Beam was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 07. 16

Beam Foundation presents: R...

TL;DR: 2019 was great, 2020 will be remarkable!2019 was a formative year for Beam, building a solid foundation of a multitude of products from the very launch. This is not a full list of the year’s achievements:TechnologyBeam wallet: desktop (Mac, Win, Linux), mobile (iOS, Android), so that you, dear users can confidentially send and receive Beam in an easy wayBeam wallet API: to power the integrations with mining pools, exchanges, and payment gatewaysBeam Atomic Swaps Marketplace (in Beta): to empower confidential exchange of Beams with BTC, LTC, and QTUM; the first privacy coin ever to achieve that.Tons of POC, each of which will get its own lane in 2020 roadmap: adapting Lelantus to Mimblewimble to break linkability and support offline sending of funds, Lightning for instant payments, Hardware wallets support, Beam Anywhere (a.k.a. Beam Web wallet as a browser plugin)We’ve revamped our website 3 times to continuously broadcast and reflect what’s going on as Beam growsWe’ve successfully completed a hard fork and straight after the 2020 New Year celebration had our first halvingWe’ve shipped over 65 releases across all our projects and platforms.Governance and CommunityAs planned from the get-go, on November 25 we have announced the establishment of a non-profit Beam Foundation that is taking over the governance of the protocol as we speak.The Foundation is run by an independent Board and it will be deploying the Treasury funds to continue further development and innovation of Beam protocol.We are actively communicating with our 50K-strong community members across various platforms. With time, the Foundation will promote more and more community involvement in governance process.Nice, but what’s up for 2020?Well, as 2019 shows, every plan is subject to change. Therefore, instead of making long plans into what we can find under the 2021 New Year tree, we’d prefer to communicate our short- and midterm plans. We’ll walk you through the diagram below, lane by lane:We will launch a family of products that will serve as a foundation for the Beam Confidential DeFi Ecosystem(again, the first of its kind in the space):Before the forkAtomic Swap marketplace will leave Beta with numerous UX fixes and API for market-makers. This will improve the liquidity and make it possible for anyone to exchange Beam for BTC, LTC, QTUM (or vise versa) confidentially, without intermediaries and with no counterparty riskLaser Beam — our Instant payments technology to eventually enable instant immediate payments, micro payments and “streaming” money use cases.Exchange rates to fiat and selected cryptocurrencies will be displayed in the Beam wallet, so you can always know how much your Beam is worth if converted to those currencies.After the forkWeb Wallet and Wallet Service API is going to be the focal point of the DeFi ecosystem, bringing Beam to every browser (and to 3rd party wallets integrations) with great user experience and without sacrificing users’ privacyConfidential Assets on Beam will allow anyone to create and transact new kinds of tokens on the Beam blockchain. These new tokens will have the same confidentiality and great user experience as the native Beam coin. Naturally, support for multiple token types will be added to Beam Wallet.Bridges to Ethereum will allow creating Beam representation of certain ERC20 tokens and creating 1-to-1 pegs of such ERC20 tokens to their representation on Beam blockchain. For example, users will be able to lock a certain amount of Dai in the Bridge’s smart contract, and get the exact same amount of bDai on the Beam Blockchain. The bDai tokens can be freely transacted between Beam wallets, and can also be transferred back to Dai at any moment. Multiple types of tokens will be supported, and more tokens can be added in the future by Bridge operators. In the more distant future, we may consider developing bridges to other blockchains besides Ethereum.Wallet Auditability — an opt-in feature in the wallet that will allow institutional and business users to seamlessly report their transactions to third parties of their choice.Later onDeFi Building Blocks. Based on Scriptless scripts technology, we will develop primitives to enable certain kinds of DeFi applications on Beam — think of Collateralized Debt Positions (CDP), lending, STO and more.Following the development of the Bridges, it will be possible to create Sidechains that will support complementary advanced technologies such as smart contracts with EOS, Ethereum, etcPrivacy enhancementsLelantus MW will be released on Mainnet. Lelantus MW dramatically increases the UTXO anonymity set and makes it virtually impossible to establish links between different UTXOs.One-side payments. Based on Leantus MW technology, one-sided payments will allow sending and receiving Beam without Mimblewimble’s interactivity requirement. Today, the receiver must come online at most 12 hours after a transaction is initiated, which may be inconvenient at times. One-sided payments remove that need.Tor/i2P will enhance layer 0 privacy beyond Dandelion++Later on:Dandelion is currently used by the nodes when broadcasting transactions to the network. However, the SBBS messages are currently sent directly by the originator. SBBS over Dandelion will help to obfuscate every message sender.Mixnet integration to further enhance layer 0 privacySecurity enhancementsLedger and Trezor support. Bringing Beam to Ledger and Trezor hardware wallets turned out to be a complex task. We spent a lot of effort on that during 2019, and we are committed to making it happen. We have recently done a lot of progress in reducing the memory footprint and computational complexity of Beam integration, which will allow support of the most popular Ledger and Trezor models.Multisig support will allow committing transactions only when approved by multiple signatures. Standard “M out of N” schemes will be implemented.UsabilityWe want to remove the current limitation of not using the same seed phrase from several wallets simultaneously, so at first, we’ll enable sync of balance and transactions history; later on, full sync (addresses, full transaction data) will be implementedNotifications about the new version for desktop wallets will come handy so you’ll always be up-to-dateMiscellaneous (others)Beamhash III will be the final Beam POW algorithm. BeamHash III is a proof of work designed to create a smooth transition from GPU mining to asics in the future. While perfectly fitted to today’s capacities of GPUs, especially their memory bandwidth, it also will allow rather simple and cost-efficient asic designs. Compared with the current BeamHash II algorithm the performance of BeamHash III is more independent of the underlying GPU architecture and less energy-consuming. Furthermore, upcoming Asics may be produced using a more power and cost-efficient chip design as well.GhostDAG consensus upgrade, when activated, will enable much better mining decentralization, faster confirmation on L1 (seconds) and much higher throughput (Transactions/sec), which will serve to keep fees low even when demand for Beam and Beam’s CAs will soar.We will continue to live up to our values of honesty, technology leadership and great usability, actively engage with our community and collaborate with other worthy projects in the space. 2020 is gonna be remarkable!Come discover Beam and join our community!Download Beam Android Wallet on Google PlayDownload Beam iOS Wallet on App StoreLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyBeam Foundation presents: Roadmap update Q1 2020 was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 07. 06

Hard Fork Completed

As announced earlier, Beam has successfully completed the second Hard Fork.At block height 777,777 the mining algorithm was changed from BeamHashII to BeamHashIIITeam Beam were all online at the time of the fork, constantly monitoring the health of the network and prepared for any contingency.While the Fork was VERY smooth it was a moment of suspense when block 777,776 was mined and we were all waiting to see the post-fork block 777,777 appear. When it happened, it was a moment of joy and pride for the team.BeforeAnticipating block 777,777AfterYou could definitely see a lot more smiles on our faces.Congrats to 2miners who found block 777,776, the last BH2 block and to Leafpool for having mined the first block with the new PoW.The first BeamHashIII block on our freely available open source pool software also happened at block 777,801 — build your own pool with this free code.AftermathAfter the Hard Fork occurred, we witnessed an expected drop in difficulty and the two main reasons being that; not all the miners had performed a timely upgrade, and that the upgraded miners participating in the new PoW were mining at lower speeds per GPU on the network — as is the design of BeamHashIII.However, only 24 hours after the fork, the hash rate of the network reached and eventually stabilised from its pre-fork value (taking into consideration that the the previous algorithm was more established with miner development and offered higher GPU mining hashrates).Why did we do the ForkWhen Beam launched on Jan 3, 2019, we announced that we will perform two hard forks. The rationale was to signal to ASIC developers that there is no point to start developing ASICs until the second hard fork is out.We timed the first fork roughly 6 months from launch, and the second one in mid 2020. The 10-month timeframe is chosen because that’s how long it usually takes to develop a new ASIC chip.What else is in this Hard ForkIn addition to the algorithm change, we implemented several important features that are consensus-breaking and can only be done as part of a Hard Fork:Activate support for Confidential AssetsActivate support for Lelantus MimblewimbleActivate support for One Sided PaymentsAcknowledgmentsWe would like to thank our wonderful community, the miners, the pools and the exchanges who worked diligently to perform the necessary software upgrades and help us pass the Hard Fork with flying colors.We also want to extend special thanks to our PoW Advisor Wilke Trei (aka Lolliedieb) who developed BeamHashI, BeamHashII and BeamHashIII.Go Beam!Come discover Beam and join our community!Download Beam Android Wallet on Google PlayDownload Beam iOS Wallet on App StoreLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyHard Fork Completed was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 06. 29

Eager Electron 5.0.2 — Andr...

Eager Electron 5.0.2 — Android— Release NotesRelease Date: June 22nd, 2020This Eager Electron 5.0.2 release paves the way for Beam towards a Confidential DeFi ecosystem.IMPORTANT: After Beam blockchain will reach block 777777 the upgrade to 5.0 is mandatory to access your funds.Features:In one word: “notifications”, in two: “decentralized notifications”! Your privacy stays solid, the wallet address won’t be exposed when any notification is received.We deliver exchange rates to USD/BTC for every amount displayed.You’ll know when the new wallet version just came out. No worries, our wallet will never auto-update — this decision is entirely in your hands.You’ll never miss the info when a transaction is completed.Too many notifications? Switch off those that you don’t need in Settings. Easily.Improvements:Getting BEAM from Beam faucet always present on the Settings screen.Fixes:Few smaller issues and crashes were resolvedKnown limitations:When restoring your funds in automatic mode, verify that your most recent transaction (from any device) was completed at least 1 hour ago. Otherwise, your restored balance may be incorrect and additional restore procedure will be required. When restoring your funds with your specific node, verify that the node is fully synchronized with the blockchain before starting the restore procedure. Otherwise, your restored balance may be incorrect and additional restore procedure will be required.Points to mention:DO NOT SIMULTANEOUSLY RUN TWO WALLETS INITIATED FROM THE SAME SEED PHRASE. No funds will be lost in any case, please read this article for full details.If you really want to run two wallets (read: geek mode), initiated from the same seed phrase, make sure each wallet is connected to the node configured with the owner key (which is derived from the seed phrase). Even if two wallets are connected with such a node which is properly configured with the owner key, the transaction history will not be synchronized among them (each wallet will see the correct balance but only its own transaction history).Come discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyEager Electron 5.0.2 — Android— Release Notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 06. 22

Eager Electron 5.0.9328  — ...

Eager Electron 5.0.9328 — Hotfix — Release NotesRelease Date: June 19th, 2020IMPORTANT: After Beam blockchain will reach block 777,777 version 5.0 is mandatory to access your funds.Fixes:Fast-sync potential problem fixInconsistent balance on mobile wallets after UTXO rescan in nodeFixed node slow-down if many shielded txs are broadcastedAttempting to restore txs after rollbackFixed possible API crash on wallet with Lelantus transactionsImprovements:Added automatic rollback limit of 60 blocksMulti-threaded Lelantus withdrawal proof generationFaster UTXO rescan in walletVerifying release binariesPGP key: “A6C6 2C9F 5593 1860 AFF8 3BBB 997E AB9F 3DF7 F375”Go to https://keybase.io/beammw and get the Public PGP key.Download the signed binary file (with extension .asc) you want to verify.Verify the signature using PGP Suite or any other PGP verification toolsCome discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyEager Electron 5.0.9328  —  Hotfix  — Release Notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 06. 19

Eager Electron 5.0.9  — iOS...

Eager Electron 5.0.9 — iOS — Release NotesRelease Date: June 12th, 2020This Eager Electron 5.0 release paves the way for Beam towards a confidential finance ecosystem. It enables multiple features that will be introduced later, such as confidential assets, breaking linkability, and many others.IMPORTANT: After Beam blockchain will reach block 777777 the upgrade to 5.0 is mandatory to access your funds.Features:In one word: “notifications”, in two: “decentralized notifications”! Your privacy stays solid, the wallet address won’t be exposed when any notification is received.We deliver exchange rates to USD/BTC for every amount displayed.You’ll know when the new wallet version just came out. No worries, our wallet will never auto-update — this decision is entirely in your hands.You’ll never miss the info when a transaction is completed.Too many notifications? Switch off those that you don’t need in Settings. Easily.Improvements:In the advanced restore flow (read: geek mode), some wordings just became better.Getting BEAM from Beam faucet always present on the Settings screen.Fixes:Few smaller issues and crashes were resolved.Known limitations:When restoring your funds in automatic mode, verify that your most recent transaction (from any device) was completed at least 1 hour ago. Otherwise, your restored balance may be incorrect and additional restore procedure will be required. When restoring your funds with your specific node, verify that the node is fully synchronized with the blockchain before starting the restore procedure. Otherwise, your restored balance may be incorrect and additional restore procedure will be required.Points to mention:DO NOT SIMULTANEOUSLY RUN TWO WALLETS INITIATED FROM THE SAME SEED PHRASE. No funds will be lost in any case, please read this article for full details.If you really want to run two wallets (read: geek mode), initiated from the same seed phrase, make sure each wallet is connected to the node configured with the owner key (which is derived from the seed phrase). Even if two wallets are connected with such a node which is properly configured with the owner key, the transaction history will not be synchronized among them (each wallet will see the correct balance but only its own transaction history).Come discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyEager Electron 5.0.9  — iOS — Release Notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 06. 12

360 roundabout on Beam UX (...

360° roundabout on Beam UX: part 1TL;DR UX is always our priority and it is a result of the team effort. In this article, I will bring multiple examples of what we did during the last 1.5 years to create a holistically great customer experience across all our products.We build BEAM altogether: we start the ideation with our design team (with Alexandra Shelenkova and Dasha Tarakanova) move on with the dev and QA teams and of course, listen all along the road to the community ideas and suggestions (honestly, sometimes the discussions can become a bit heated, yet it’s always for the better good as every participant cares a lot about the success of our platform).Meet and greetWe want everyone to feel at home from the first time they try to google BEAM or to use our products such as wallets, miners, etc.Our website is a good source of information to start learning what BEAM is. We’ve created a dedicated page for every visitor type:Regular visitors can read about our wallets’ features before downloading the wallets. And when they have some money, they can always pay with BEAM for all kinds of e-commerce stores.Miners are equipped with everything necessary to consider BEAM and to start mining.Traders can easily find where to buy BEAMThose who aim to take an active part in what happens in BEAM, are invited to join BEAM ambassador programWe also want you to recognize any BEAM-related product from a distance. Therefore, we’ve developed a consistent visual fingerprint for business cards, website, wallets, BEAM explorer, artworks for BEAM-related articles and even for the Telegram stickers :)Continuous supportOur online presence attends several important aspects:We keep you updated on everything that happens in the media of your choice: articles, tweets, videos, posts, and many other channels. We are ready to meet you where you feel most comfortable.We want you to feel confident using BEAM, our support channels for regular users, miners, and developers help people with issues of every sort. I dare to say that we provide world-class customer support FOR FREE: no Zendesk, no case numbers, no bullsh$t emails like “we’ll get back to you within 48 hours” sent from a no-reply address.Our support team constantly listens and replies to the Telegram channels during the working hours. The representatives are core team members (QA, devs, DevOps, etc), so you’ll get the info from the first hand of those who smell and breathe BEAM even while they sleep. We want your problems solved fast and with competence.We also maintain a special journal to find the common cases that need to be tackled at the product level.Easy-to-use walletsIn simple words, we want to gracefully meet the needs of regular, non-geeky users.In this (longer) section I will bring many concrete examples on how we’ve managed to tailor a friendly face to the monstrous set of technologies that hide under the hood (e.g. Mimblewimble, Lelantus-MW, Atomic Swaps, etc, etc).Let’s start from reviewing our general UX guidelines:Every feature should work as seamlessly as possible: whenever a wallet can make a decision automatically, no need to ask the user. From his point of view, it just works.For every user message, communicate in non-tech terms. No exceptions (well, almost none — and we’re proud of how close we got).Optimize for the common scenario. Decide the defaults to enable the common needs first. Move the unnecessary switches to advanced sections (or remove them altogether). Don’t provide unnecessary flexibility (indeed, good UX is frequently about what should not be done rather than having a bloated aircraft deck). Advanced scenarios are allowed but not at the expense of the common scenarios.To the examples now. As a game, try to see which principles revealed themselves for every case :)Let the wallets talk, not peopleTo create a Mimblewimble transaction, to send money from one wallet to the other, the wallets need to “talk” directly with each other. Some projects direct users to exchange files or snippets over emails or messengers. Beam Team implemented the short-term storage (called SBBS a.k.a. Secure Bulletin Board System), through which the wallets can securely broadcast messages to each other.A wallet got to do what a wallet got to doIn the first versions of the wallet, there was an option to mine BEAM. How cool was that! Earn money straight from your wallet. However, we’ve quickly realized that these two functional requirements are relevant to very different user profiles. Moreover, mining BEAM on CPU is proven to be very uncompetitive to GPU mining. Also, the heavy calculations were eating the CPU mercilessly (and also the battery). We’ve taken the miner out and never looked back.Display % and times on loading, not the number of blocksWhen the wallet is synchronizing with the network, the time left is continuously calculated and displayed. The tech team advocated for a more straightforward choice, to display the number of blocks left to download. But “blocks” are insignificant for the end-user (and the wallet load process consists of 3 stages the naive user doesn’t need to care about), therefore, after a few versions, the time approximation algorithm was tuned nicely and the estimated times displayed became fairly accurate.Isolate the technical partsThose who understand blockchains know that digital money is represented by so-called UTXO (an abbreviation of “Unspent Transaction Output”, the word “transaction” is abbreviated as “tx” in technical circles). Each UTXO can have a monetary value plus additional parameters (and this is not a place to elaborate on them).Every user wants to know the balance at each point in time. But this part is tricky: if you have a single UTXO of 10 BEAM and you want to send me only 2, the UTXO needs to split into 2 and 8. 2 will be sent to my wallet and 8 will be returned to you when the transaction is complete. Some technicalities cannot be easily skipped.We wanted to display UTXO for debugging purposes (especially for the first versions of the wallet), yet we’ve syndicated all the UTXO related information on a single screen that might be removed later with little consequence for the rest of the system.We still have a remnant of functionality when displaying the change as a part of an outgoing transaction to the sender, but that would be it.Putting privacy on the spotlightBEAM is a privacy coin. Meaning that our wallets should project the vibe. The dark theme was a conscious choice (our mobile wallets become even darker at night).I’ve lived 4 years in Thailand, where people transfer money to each other via banking apps, in seconds (in Israel, my home country, that ease of use is yet about to happen). When I transfer money to someone, I want him to look at my screen to double-check that the transaction details such as name or amount are correct. However, I don’t want him to see my balance.Mobile wallets got an “eye” button that hides the total amounts of funds, leaving the essential details observable for validation by both sides.Have a fresh wallet? Try it with some real money!BEAM faucet (a great community product) can provide wallets with a small amount of real BEAM to play with. Moreover, our mobile wallets are integrated with the faucet, pre-charging the wallet with several taps.Making seed phrase less painfulMobile wallets should be used literally on the go. If you’ve met someone on the bus, telling you about BEAM for the first time, you should be able to install the wallet with one hand :) To ease the onboarding, the mobile wallets do not enforce seed phrase verification while the amount kept in the wallet is small enough.Node connectivity? Never heard of it!In the past, when the wallet was connecting the peer nodes, it was a lottery: the node might not be the closest geographically, also the node might stop responding and the message to the user was displayed offering him to connect to some other node. How insensitive! Why should he bother at all?The smarter algorithm was implemented to determine the best node to connect to. The same functionality is used when node disconnects to find the next best node to work with. Fix the problems fast, under the good, and keep the boss calm. You, our dear user are the boss.For the geeky professionals, we allow tweaking some advanced settings if they want to.Extendable UI: same screen, greater power!Till v4.0 (a.k.a. Double Doppler) our wallets were communicating using addresses. “Address” is a friendly and understandable word, nice and simple.With Atomic Swaps wallets needed to pass more information (such as exchange rate, offer expiration time, currencies to swap with, etc). This information was encoded in what we’ve named “transaction token”. The token looks similar (but is longer than a regular address) and embraces all the relevant information to start the transaction.Later on, at 4.2 and 5.0, the regular transactions started to carry several data pieces (such as Wallet ID, which is beyond the scope of the article). Therefore, addresses will be replaced with tokens everywhere. Well, almost.The exception is with never expiring addresses when communicating with exchanges or mining pools. As these are more reluctant to re-implement the infrastructure code, the wallet will still leave an option to create an address instead of a token for the special case.Keep the user informed without revealing his privacyTo keep the link between “normal” and crypto worlds, the user should always know how many coins he has in the terms, close to his everyday currency.We’ve implemented decentralized notifications using the same SBBS system mentioned above. The amounts of balance, send, receive can be displayed in both USD or BTC. And, due to the right technology, the wallet IP address is not exposed.The same mechanism is used when a new wallet version is released.Complex things should look simpleAtomic Swaps idea sounds simple: you send me BTC to get BEAM in return. But the underlying functionality isn’t that straightforward: two blockchains need to be orchestrated by a state-of-the-art state machine (really, our wallet was reimagined when we’ve introduced that feature) to enable both funds’ transfer securely and without a leak.However, as always, we wanted to screen the technicalities from the user. Therefore, dynamic statuses were introduced to tell the user what will happen in simple words like timeouts and expected outcomes. Few examples:The swap is expected to complete in 10 minutes at mostIf nobody accepts the order in 10 minutes at most, the offer will be automatically canceledSwap failed, the money is being released back to your walletHere’s the punch: the number of minutes (hours, seconds) is dynamic. We’ve liked the idea so much that we’ve enriched the regular transaction statuses with the same dynamic information:If the receiver doesn't get online in 10 minutes, the transaction will be canceled.It is taking longer than usual. In case the transaction could not be completed it will be canceled automatically in 10 minutes.Bottom line: BEAM wallet users know what to expect at any given moment.ConclusionThis article was inspired by some of the great ongoing discussions in the Beam Community telegram channel about BEAM Wallets’ usability. I hope that now the reader understands BEAM UX direction way better than before.In my next article, I’ll describe features that are yet to come to BEAM. So, before you run to our channels to suggest something, please stay tuned for a bit longer and get aligned with what we already know :)Come discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacy360 roundabout on Beam UX (part 1: past) was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 06. 03

Eager Electron 5.09146.2863...

Eager Electron 5.0.9146.2863 — Release NotesRelease Date: May 28th, 2020IMPORTANT: Before upgrading to 5.0 all Atomic Swaps need to be concluded or cancelled and all open Laser Beam channels need to be closed!This 5.0 (Eager Electron) release paves the way for Beam towards a confidential finance ecosystem, enabling multiple features in CLI that will be introduced later in UI wallets such as confidential assets, breaking linkability, and many others.After Beam blockchain reaches the block 777777 the upgrade to 5.0 is mandatory to access your funds.Important information for Exchanges and Mining Pools: Confidential Assets-related functionality (e.g. send/receive etc.) is disabled by default. To enable explicitly, use - enable_assets command-line option when running BEAM API or BEAM wallet CLI. Please read the complete tutorial here.Features:[miner, node] BeamHash III - the new, the great, and the last POW algorithm for Beam[cli] Break transactions linkability with Lelantus MW (for Beam and any CA)[cli] Non-interactive transactions[cli, api] Issue, burn and transfer Confidential Assets (disabled by default)Improvements:[node] Added an option to manually specify preferred peers for rare edge cases[api] The number of confirmations is now available to the transaction sender and receiver[desktop wallet] Introduced new and more informative “failing” status for Atomic Swaps when the transaction is rolling back[desktop wallet] The default offer expiration for Atomic Swaps was extended from 30 minutes to 12hFixes:[desktop wallet] Wallet update notification will not be displayed if a wallet was… (surprise) already updated.[api] swap_offer_list command provides the list of offers as expected.Other:[desktop wallet] Infrastructure change: the UI code was extracted to a separate repository to speed-up the development and QA process in the futureKnown limitations:When using active laser beam channels the wallet should not be offline for over 24 hoursAtomic Swaps of Confidential Assets with BEAM/BTC/LTC/QTUM will be released later onPoints to mention:In case a mobile wallet is connected to a random node and the user has both mobile and desktop wallets that are using the same seed phrase, the funds sent to the desktop wallet won’t appear on the mobile wallet. If the desktop wallet is running a local node, it will see funds sent to both wallets. The reason is that the local node (integrated into the desktop wallet) always monitors the blockchain for UTXOs related to the seed of the wallet. The mobile wallet does not run a local node and thus can only monitor transactions sent to its specific SBBS addresses. Of course, no funds will be lost in any event.BEAM wallets won’t display received Confidential Assets and amounts kept in the shielded pool. Please use CLI or API till the future notice.For a more comprehensive list of the tasks accomplished please read here: https://github.com/BeamMW/beam/projects/28Verifying release binariesPGP key: “A6C6 2C9F 5593 1860 AFF8 3BBB 997E AB9F 3DF7 F375”1. Go to https://keybase.io/beammw and get the Public PGP key.2. Download the signed binary file (with extension .asc) you want to verify.3. Verify the signature using PGP Suite or any other PGP verification toolsCome discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyEager Electron 5.09146.2863  —  Release Notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 05. 28

We Asked, You Answered

Earlier this week, we asked the community an important question regarding Confidential Assets, which will be activated in the upcoming Hard Fork, with integration in the GUI wallet to soon follow.This is an important milestone for Beam, in paving the way to a fully fledged confidential DeFi ecosystem. Confidential Assets will benefit from the scalability, privacy, and usability that Beam benefits from. They will also be easily tradable via atomic swaps, with both Beam, and supported currencies, right from within the wallet.Not only do the Confidential Assets benefit from Beam’s already sensational features, but those introduced post fork, and into the future. They will also open the doors for some incredible use cases to come to fruition. From Confidential Synthetics like gold, to digital assets like stocks, and bonds, to Confidential Wrapped Assets such as BTC and ETH, the possibilities are endless.This being said, they also introduce the possibility that the chain is bogged down with needless assets, with little use and innovation, much like the thousands of erc20 tokens on Ethereum. In order to combat this, an amount of BEAM will be required to issue a new asset on top of Beam, and this is where we took it to the community.We opened a survey, to get the communities input on how many Beams should be locked in order to create an asset. Let’s take a look at what the community said…The numbers:Range:0.01 BEAM - 1000000000 Beam :DWeighted Average (with outliers removed):3143.902439The Questions:There were a number of great questions regarding the lock amount, and ideas on how to make it work. Below are the most common questions that the community asked.Can the lock amount be denominated in USD, rather than BEAM? This could not be done without introducing a central point of control and potential failure. For this reason, we did not consider this as a viable option for asset issuance.Can the lock amount reduce over time? This adds more complexity to the lock model, and in a sense, potentially disincentivizes early adopters of Confidential Assets, as the amount of BEAM required would reduce with time.What if the price of BEAM is to increase and thus make confidential asset issuance unaffordable? The BEAM lock amount for Confidential Assets will be set after the upcoming Hard Fork. This does not mean the amount will stay the same forever, but to change it will require a Hard Fork.What if developers are unable to put up the lock amount for confidential asset issuance? If this happens, there will be the opportunity in the future to provide grants for serious projects looking to issue assets on Beam.So with all that out the way… what is the lock amount?Given that the question was put to the community, the best decision seems to be to make that voice heard.The lock amount for Beam Confidential Assets will be set at 3000 BEAM.This figure is inline with the weighted average from the community survey, putting the outcome in all of our hands. It is an absolute privilege to have such a strong, supportive community, willing to engage in discourse of the pros and cons of such things, and this is something that will be happening a lot more moving forward.Team BeamContactAny feedback? Any question? Any concern or problem?Contact Team Beam:Telegram Support ChannelTelegram Community ChannelEmail SupportCome discover Beam and join our community!Download Beam Android Wallet on Google PlayDownload Beam iOS Wallet on App StoreLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyWe Asked, You Answered was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 05. 28

Double Doppler 4.2.8635 — H...

Double Doppler 4.2.8635 — Hotfix — Release NotesRelease date: April 22General Notes:In some cases, the wallet can take up to 20 minutes for converting databases to the new format on the first start after update.We recommend finishing all ongoing transactions and swaps before upgrading to a new versionFixes:[desktop wallet, cli wallet, api] Atomic Swaps — Node height incorrect validation on swap progressKnown limitations:When using active laser beam channels the wallet should not be offline for over 24 hoursPoints to mention:In case a mobile wallet is connected to a random node and the user has both mobile and desktop wallets that are using the same seed phrase, the funds sent to the desktop wallet won’t appear on the mobile wallet. If the desktop wallet is running a local node, it will see funds sent to both wallets. The reason is that the local node (integrated into the desktop wallet) always monitors the blockchain for UTXOs related to the seed of the wallet. The mobile wallet does not run a local node and thus can only monitor transactions sent to its specific SBBS addresses. Of course, no funds will be lost in any event.Come discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyDouble Doppler 4.2.8635 — Hotfix — Release Notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 04. 22

Beam Hard Fork Announcement

Beam will execute the second hard fork as previously announced in our Roadmap.This network upgrade will occur at Block Height 777777, expected to be reached on 28 June 2020.Breaking changesPoW algorithm will change from BeamHash II to BeamHash III. More details on BeamHash III will be shared closer to the time.Activate support for Confidential AssetsActivate support for Lelantus MimblewimbleActivate support for One Sided PaymentsTimelineCompatible releases of node, wallet, and miner will be versioned Eager Electron 5.0.The Node and the Desktop Wallet binaries will be released around the end of May, 2020 to allow everyone approximately 30 days to upgrade to the new version.The Mobile Wallets for Android and iOS will be released a little later.All users will only need to upgrade their software to the latest version.The binaries will support the current blockchain, and will automatically switch to the new consensus mechanism when the target block height is reached. No user intervention will be required. Funds will not be affected.CompatibilityAfter the Block Height 777777 is reached, wallets earlier than 5.0 will stop working. The users will need to upgrade the wallets to version 5.0 or later to access the funds.So, What does all this mean for Beam miners?Is BeamHash III going to be a great improvement to the Beam mining network and is it better for GPU mining and GPU miners?Yes! The wider memory operations in the design of BeamHash III allow better use of the fuller capabilities of a GPU card. Making it easier to saturate the given bandwidth of the GPU card, reducing the potential advantage of other devices, especially FPGAs.The stronger algorithm binding of the new scheme utilised in BeamHash III will make ‘unknown optimisations’ potentially used for secret mining, more unlikely. Enhancing the network with what we hope to be 100% GPU mining (for the foreseeable future, at least) and ensuring any FPGA would be much similar sol/watt as the fastest of GPU mining cards.Since this is to be the final anticipated algorithm change, how then, can GPU’s compete with any potential ASIC devices which may be designed for BeamHash III in the future?Well, ASIC chips are often strong in compute operation to force the calculations of a particular algorithm to be faster and in turn give a mining device more ‘speed’ (aka hashrate), for less power. The lesser compute dependency of BeamHash III reduces the potential advantage of multi-chip Asics over GPUs whilst also allowing GPUs to run lesser clock rates, for more improved calculation ‘speed’ (hashrate). The reduced solution size compared to Equihash 150/5 allows us to give more room for the nonce without increasing the block header size.If an ASIC is eventually produced which is able to handle BeamHash III, it would need to have a smaller compute fraction than that which is generally used for ASIC design. For multi-chip ASICs, that means that these would only have a tiny custom-designed chip which can in turn be made rather cheaply, because the main costs would come from the required memory and not as is generally utilised in expensive ASIC machines, from the compute chip.For a single chip ASIC (and to note, this is not yet feasible with 7nm structure), the development costs would be much lower per chip (where production and yield would increase costs) and thus would likely not be economically feasible. Whilst nobody can predict how that fabrication might change in the future and it is possible that some ASICs may come into production, overall, BeamHash III certainly gives us some time until such ASICs are cost-effective. When multi chip ASICs do come, we can expect them to at least be affordable for miners who are keen to support the Beam network.Ultimately, A single chip ASIC will invariably win in terms of sol/s per watt and also in terms of speed. But we have made it hard enough to build such a thing… At least, it’s not currently achievable.What do miners have to do for the Hard Fork?It’s important for us to make this switch for miners as seamless as possible. For this reason, we will release Eager Electron 5.0 in advance that will automatically switch to the new BeamHash III consensus at the appropriate block height, 777777. We will work closely with miner software developers and pool operators to encourage/ensure that you all you need is up to date and ready. So for miners, you can simply update your wallets and mining software prior to the hard fork height, and be switched over when the time is right, sit back, and keep on hashing!ContactAny feedback? Any question? Any concern or problem?Contact Team Beam:Telegram Support ChannelTelegram Community ChannelEmail SupportCome discover Beam and join our community!Download Beam Android Wallet on Google PlayDownload Beam iOS Wallet on App StoreLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyBeam Hard Fork Announcement was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 04. 22

Double Doppler 4.2.8632— Re...

Release Date: April 16th, 2020General Notes:In some cases, wallets can take up to 20 minutes for converting databases to the new format on the first start after update.We recommend to finish all ongoing transactions and swaps before upgrading to a new version.Release NotesFeatures:[desktop wallet] In one word: “notifications”, in two: “decentralized notifications”! We did it right, the wallet address won’t be exposed when any notification is received. The wallet will nicely tell you about transaction completion or when it’s time to update the wallet to a new version. No worries, our wallet will never auto-update — this decision is entirely in your hands.[desktop wallet] Exchange rates to USD/BTC. Under the hood we use the same decentralized notifications infrastructure, hence again, your privacy stays solid.[api] Atomic Swap API for market-makers. Build your systems to manage decentralized atomic swap orders![infrastructure] Wallet Identity was added to proof and ensures that the transaction is performed between claimed participants.[cli wallet] Laser Beams for instantaneous BEAM transferImprovements:[desktop wallet] Payment proof added when transaction history is exported[desktop wallet] Add All button when sending BEAMFixes:[desktop wallet] “Where to buy BEAM” button is back!Over 90 tasks accomplished in total, for more details please see here: https://github.com/BeamMW/beam/projects/25Known limitations:When using active laser beam channels the wallet should not be offline for over 24 hours.Points to mention:In case a mobile wallet is connected to a random node and the user has both mobile and desktop wallets that are using the same seed phrase, the funds sent to the desktop wallet won’t appear on the mobile wallet. If the desktop wallet is running a local node, it will see funds sent to both wallets. The reason is that the local node (integrated into the desktop wallet) always monitors the blockchain for UTXOs related to the seed of the wallet. The mobile wallet does not run a local node and thus can only monitor transactions sent to its specific SBBS addresses. Of course, no funds will be lost in any event.Come discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyDouble Doppler 4.2.8632— Release Notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 04. 17

Beam Logo: from magic to th...

A long time ago in a galaxy far far away… Wow, stop! It’s another story…Mr. and Mrs. Dursley, of number four, Privet Drive, were proud… it’s not that either.. although there seems to be something similar there…Aha, Beam! That’s right =)As a part of our series of articles about Beam evolution, let me share how the company visuals evolved. You might have noticed how our website www.beam.wm has been changed during the last 18 months. But now I want to tell you the story of the most recognizable element of our brand — the logo.When most of our users hear “Beam”, they identify it with a prism. And this is absolutely true. But in the very beginning, Beam had a different vision of what should be the “Beam” brand. So let’s see how it started.I — Harry Potter times ✨In the first half of 2018, the word “Mimblewimble” was common enough in the crypto world. The Beam team selected the Mimblewimble protocol as a foundation for our blockchain. The Mimblewimble name naturally pushed the first version of our branding towards the Harry Potter theme.Here we are, the first version of the logo with the ⚡️lightning ⚡️symbol, a long time before I joined Beam.However, we create high-tech things, not a kind of magic or witchcraft. Time to level-up, stay tuned.II — The dark side of the moon times 🌒What associations come to your mind when you hear the word “Beam”? “Beam” as a construction block? “Beam” like a drink? “Beam” like a ray of light? We chose the last one and the logo came to life. Everyone was excited with the logo inspired by a dispersive prism where all colors of light merge and hide in the white. This is our allegory of the concept of privacy.… Have you ever seen how a beam of light goes through the prism and splits into 7 different colors? It’s amazing, it’s magic. Yet do you remember we decided to create technology, not magic, so the logo was converted into more techie style: facets, colors, gradients, rays direction…In the middle of 2018, Beam started to use the prism logo for the first time. Here’s how it looked:This logo defined the brand colors which are in use till today (well, with slight variations).III — Good old times 📻When the desktop wallet launch was approaching, we started to work on a slicker version of our logo. Alexandra, our Design Lead, suggested numerous versions of the logo. There were many discussions and brainstormings about how the Beam logo could look. The discussion’s log would comprise material for another article 😅. Here are some of the suggested ideas which were not accepted:In our new logo, the playful multicolored gradients gave space to more respectable and trustworthy touches. The logo became more minimalistic and better recognizable. The color scheme shifted from pink/violet to green/blue. Do you want to know why?First of all, green is the most readily perceived color. Second, green is all about harmony, balance, and peace. We want our users to stay calm and trust our product. Third, blue is a color of confidence, control, logic, honesty, and freedom. Neon cold colors are associated with reliability and stability. As Beam is! Finally, we’ve topped it off with pink/violet, a little bit of creativity, extravagance, and fantasy. Let me introduce the updated logo:The dark background wasn’t chosen by chance. It is strongly associated with privacy. We knew that using a dark background would pose some limitations, however, we’ve optimistically “let the worries go”. Later we faced a problem — the logo downloaded from our web-site was most often pasted on light backgrounds.Here are some not-so-pretty examples of using our logo on various backgrounds:Side note: we created a media kit that can be easily downloaded from the Beam website. The logo pack there includes guidelines with different scenarios of Beam logo in various contexts. For example, it includes a logo with a transparent background which we strictly recommend to use only on dark background. To download the media kit click the right mouse button on the logo or choose Media Kit from the Resources menu.IV — Welcome to the new decade 🎆After a dozen releases for Desktop, Android and iOS wallets it was the time to improve the current logo. The logo should become even better balanced (or should I even say “pixel perfect”). There are only a few tiny changes that I made in this most recent iteration:The raysGradient has the same angle on each ray: it makes them fade evenlyThe white ray became wider so that both sides of the prism look more balancedThe colorsJust became brighterThe fontThe letter geometry was modifiedThe font became bolderHere are all the logo versions for final comparison:This is how it looks on our printed products:So, for the time of writing, this is the most recent version of the Beam logo. We do not promise that it won’t change in the future. But we can promise you, we will continue to improve!Stay tuned and you know where to find us 🤩Come discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyBeam Logo: from magic to the new decade progress was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 03. 09

UX++ for Beam mobile wallet...

Hey again and long time no see since part 2 and part 1! While our core team is focusing on groundbreaking features like Confidential Assets, Lelantus (adapted for Mimblewimble), Atomic Swaps API, Web Wallet, and much more, I dare to say that our mobile wallets are continuously being polished on a finer level, gathering the feedback along with shorter iterations.So, what’s in the box for 4.0 (iOS, Android) and 4.1 (iOS, Android) versions?☀️ FeaturesWe 💙 you, our dear newcomers! Therefore, we made the wallets usable straight after they are installed from wherever you are. What was a hassle? Imagine installing the wallet while commuting and trying to re-type the essential seed phrase with one hand while holding the handrails with the other. This stage is not mandatory anymore! With a better balance between the risk and usability, after the installation, you’ll be painlessly directed to the main wallet screen. We want you to try the wallet first and the essential security measure (e.g. the seed phrase validation) will be postponed till enough balance is accumulated. In case you’ll want to validate it from the get-go (e.g. before the incoming transaction) — trigger the process manually from the Settings.When the right time comes you’ll see the automatic reminder to validate the seed phrase (and you won’t be able to escape the message this time)Once the wallet is installed, we want you to see how convenient it is right away. With a few magic taps, you’ll be taken to the Beam faucet web page (developed by the Beam community member vsnation [Twitter]) where a fraction of an actual Beam will be delivered straight to your wallet. Experience how fast BEAM transactions are, exchanging some money with your friends straight from the get-go.While prioritizing the essential features first, we do realize the importance of being in the right trend :) Jokes aside, the dark mode is not only conceptually related to privacy, it also tunes the wallet into the better eye-pleasing mode at night time or under low light conditions.Mobile phones come and go and, as you should know, Beam is a privacy coin based on Mimblewimble protocol, so your transaction history is not stored on the blockchain. Therefore, we’ve introduced the data import/export functions that allow transferring your Beam wallet data from one device to the other.We continuously listen for the new features suggestions on our support and community Telegram channels. Some of you were frustrated that to wipe off the wallet data, one needed to create a new seed phrase, re-initializing the wallet state. Well, we’ve just introduced the item in Settings that wipes everything with a few taps (including the “Are you sure?” dialog).🆒 ImprovementsOn a smaller scale, few neat things are worth noticing:Since more and more functionality is being added to the wallet (each with its own item in the Settings), we’ve reorganized the screen into better-grouped sections.When the wallet is re-opened, you are required to enter the password. So far, if the password has been forgotten the only way to access your funds was to reinstall the wallet and initialize it from your seed phrase. From now on, you can just trigger the restore function from the password screen.Want to use the transaction details somewhere (amount, addresses, etc), but the “fancy”-looking transaction receipt doesn’t allow to copy-paste the actual numbers? Use transaction details from the contextual menu and prosper!For the impatient, transaction screen refreshes when you pull it downTo simplify the support procedure, the wallet version number is always shown on login and restore screens.🛠 FixesAll kinds of smaller things: typos, color corrections, elements’ placement, refined explanations were done to make the wallet more intuitive and simple to use.✅ That’s it for nowMore functionality is coming (e.g. displaying rates in BTC/USD is one good example of many), stay tuned, let your friends try the wallet which just became easier to use, and tell us how we can do even better. Thanks for reading till here and see you again :)Confidentially yours, Beam Product, Development and QA teams.Come discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyUX++ for Beam mobile wallets (part 3) was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 03. 02

Double Doppler 4. 1— Androi...

Double Doppler 4. 1— Android — Release notesRelease Date: February 17th, 2020GeneralRelease notesFixesTypos, explanatory messages, elements placements, colors — all to make the app more eye-pleasing and more intuitive to use.Known limitationsWhen restoring your funds in automatic mode, verify that your most recent transaction (from any device) was completed at least 1 hour ago. Otherwise, your restored balance may be incorrect and additional restore procedure will be required.When restoring your funds with your specific node, verify that the node is fully synchronized with the blockchain before starting the restore procedure. Otherwise, your restored balance may be incorrect and additional restore procedure will be required.Points to mentionDO NOT SIMULTANEOUSLY RUN TWO WALLETS INITIATED FROM THE SAME SEED PHRASE. No funds will be lost in any case, please read this article for full details.If you really want to run two wallets (read: geek mode), initiated from the same seed phrase, make sure each wallet is connected to the node configured with the owner key (which is derived from the seed phrase).Even if two wallets are connected with such a node which is properly configured with the owner key, the transaction history will not be syncronized among them (each wallet will see the correct balance but only its own transaction history).Double Doppler 4. 1— Android — Release notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 02. 20

Double Doppler 4.1 — iOS — ...

Double Doppler 4.1 — iOS — Release notesDate of release: February 10th, 2020GeneralRelease notesFixesTypos, explanatory messages, elements placements, colors — all to make the app more eye-pleasing and more intuitive to use.Known limitationsWhen restoring your funds in automatic mode, verify that your most recent transaction (from any device) was completed at least 1 hour ago. Otherwise, your restored balance may be incorrect and additional restore procedure will be required.When restoring your funds with your specific node, verify that the node is fully synchronized with the blockchain before starting the restore procedure. Otherwise, your restored balance may be incorrect and additional restore procedure will be required.Points to mentionDO NOT SIMULTANEOUSLY RUN TWO WALLETS INITIATED FROM THE SAME SEED PHRASE. No funds will be lost in any case, please read this article for full details.If you really want to run two wallets (read: geek mode), initiated from the same seed phrase, make sure each wallet is connected to the node configured with the owner key (which is derived from the seed phrase).Even if two wallets are connected with such a node which is properly configured with the owner key, the transaction history will not be syncronized among them (each wallet will see the correct balance but only its own transaction history).Double Doppler 4.1 — iOS — Release notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 02. 10

Double Doppler 4.0 — Androi...

Double Doppler 4.0 — Android— Release notesDate of release: January 29th, 2019GeneralRelease notesFeaturesThe wallet just got much easier to use for the first-timers: the seed phrase verification is delayed till significant funds are transferred to the wallet.The wallet just became prettier at night, enjoy the dark mode!Export/import transaction history, tags, addressesThe current wallet data can be cleared with a few clicksFace unlock biometrics authentication for the happiest Pixel 4 usersImprovementsThe settings screen just became much better organizedWhen a password is forgotten the user is offered to restore the wallet with a seed phrase (or to create a new wallet)Transaction details can be easily copiedWhen pulling the screen down transaction list is refreshedThe version number is added on login and restore screensFixesMany fixes of typos, explanatory messages, elements placements, colors — all to make the app more eye-pleasing and more intuitive to use.Known limitationsWhen restoring your funds in automatic mode, verify that your most recent transaction (from any device) was completed at least 1 hour ago. Otherwise, your restored balance may be incorrect and additional restore procedure will be required.When restoring your funds with your specific node, verify that the node is fully synchronized with the blockchain before starting the restore procedure. Otherwise, your restored balance may be incorrect and additional restore procedure will be required.Points to mentionDO NOT SIMULTANEOUSLY RUN TWO WALLETS INITIATED FROM THE SAME SEED PHRASE. No funds will be lost in any case, please read this article for full details.If you really want to run two wallets (read: geek mode), initiated from the same seed phrase, make sure each wallet is connected to the node configured with the owner key (which is derived from the seed phrase).Even if two wallets are connected with such a node which is properly configured with the owner key, the transaction history will not be syncronized among them (each wallet will see the correct balance but only its own transaction history).Double Doppler 4.0 — Android— Release notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

20. 01. 29

Double Doppler 4.0 — iOS — ...

Double Doppler 4.0 — iOS — Release notesDate of release: December 23rd, 2019GeneralRelease notesSupported PlatformsAll devices running iOS 11.0 and higherFeaturesThe wallet just got much easier to use for the first-timers: the seed phrase verification is delayed till significant funds are transferred to the wallet.The wallet just became prettier at night, enjoy the dark mode!Export/import transaction history, tags, addressesThe current wallet data can be cleared with a few clicksImprovementsThe settings screen just became much better organizedWhen a password is forgotten the user is offered to restore the wallet with a seed phrase (or to create a new wallet)Transaction details can be easily copiedWhen pulling the screen down transaction list is refreshedVersion number is added on login and restore screensFixesMany fixes of typos, explanatory messages, elements placements, colors — all to make the app more eye-pleasing and more intuitive to use.Known limitationsWhen restoring your funds in automatic mode, verify that your most recent transaction (from any device) was completed at least 1 hour ago. Otherwise, your restored balance may be incorrect and additional restore procedure will be required.When restoring your funds with your specific node, verify that the node is fully synchronized with the blockchain before starting the restore procedure. Otherwise, your restored balance may be incorrect and additional restore procedure will be required.Points to mentionDO NOT SIMULTANEOUSLY RUN TWO WALLETS INITIATED FROM THE SAME SEED PHRASE. No funds will be lost in any case, please read this article for full details.If you really want to run two wallets (read: geek mode), initiated from the same seed phrase, make sure each wallet is connected to the node configured with the owner key (which is derived from the seed phrase).Even if two wallets are connected with such a node which is properly configured with the owner key, the transaction history will not be syncronized among them (each wallet will see the correct balance but only its own transaction history).Double Doppler 4.0 — iOS — Release notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

19. 12. 23

Double Doppler 4.1.6978 — R...

Double Doppler 4.1.6978 — Release notesRelease date: December 19th, 2019GeneralThis release introduces significant usability improvements for Atomic Swaps for BTC, LTC, and QTUMRelease notesFeatures[desktop wallet] Connecting to random electrum node (for BTC, LTC, and QTUM) is supported, now you can start playing with Atomic Swaps in a nearly-seamless way[desktop wallet] One step closer to business users: transaction history can be exported to a nice CSV for accounting and bookkeepingImprovements[desktop wallet] Estimated transaction fee is displayed for the BTC/LTC/QTUM receiving side[desktop wallet] Node connection indicator (for BTC, LTC, and QTUM) provides detailed information on connectivity issues[desktop wallet] The wallet will display a lock icon near “online” status when the connected node is trusted (ie set up with the wallet’s owner key)[desktop wallet] Reworked filters on Atomic Swap screen: you’ll click less to get any desired slice of information[desktop wallet] Owner key is securely shown in settings[desktop wallet] Transaction status messages became more informative in some cases, so you’ll know what is going on and what to expect for the next step[desktop wallet] Settings screen looks nicer[desktop wallet] Atomic swap offers expiration times became much shorter to align with the general market dynamicsFixes[desktop wallet] A graceful error message is returned now when a user tries to connect to an Electrum wallet with Segwit seed phrase[cli wallet] Regular and swap transaction statuses are displayed correctly[desktop wallet] The wallet starts much faster now thanks to more effective node database processing[desktop wallet] Exchange rate is always displayed as BEAM to BTC, LTC, QTUM for Atomic Swaps[desktop wallet] If the Electrum node is disconnected during active transactions, the alternative node address can be submitted in SettingsOver 70 tasks accomplished in total, for more details please see herePoints to mentionIn case a mobile wallet is connected to a random node and the user has both mobile and desktop wallets that are using the same seed phrase, the funds sent to the desktop wallet won’t appear on the mobile wallet. If the desktop wallet is running a local node, it will see funds sent to both wallets. The reason is that the local node (integrated into the desktop wallet) always monitors the blockchain for UTXOs related to the seed of the wallet. The mobile wallet does not run a local node and thus can only monitor transactions sent to its specific SBBS addresses. Of course, no funds will be lost in any eventCome discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyDouble Doppler 4.1.6978 — Release notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

19. 12. 19

Double Doppler 4.0.6818— Ho...

Double Doppler 4.0.6818— Hotfix — Release notesRelease date: December 5th, 2019GeneralRelease notesAtomic Swaps is an advanced feature, currently in beta.DO NOT USE SWAPS FOR LARGE AMOUNTS OF MONEYFor Electrum use only Legacy seed type (we do not support Segwit)For Bitcoin use version Bitcoin Core v0.17.1For Litecoin use version Litecoin v0.17.1FixesAdded support for electrum servers without full TX’s data #1141Known limitationsInconsistent transaction statuses when running two or more wallets that use the same wallet.db file cloned manuallyIf multiple wallets are restored from the same seed phrase, transaction history and addresses will not be shared among the walletsPoints to mentionIn case a mobile wallet is connected to a random node and the user has both mobile and desktop wallets which are using the same seed phrase, the funds sent to the desktop wallet won’t appear on the mobile wallet. If the desktop wallet is running a local node, it will see funds sent to both wallets. The reason is that the local node (integrated into the desktop wallet) always monitors the blockchain for UTXOs related to the seed of the wallet. The mobile wallet does not run a local node and thus can only monitor transactions sent to its specific SBBS addresses. Of course, no funds will be lost in any event.Verifying release binariesPGP key: “A6C6 2C9F 5593 1860 AFF8 3BBB 997E AB9F 3DF7 F375”Go to https://keybase.io/beammw and get the Public PGP key.Download the signed binary file (with extension .asc) you want to verify.Verify the signature using PGP Suite or any other PGP verification toolsCome discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyDouble Doppler 4.0.6818— Hotfix — Release notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

19. 12. 05

Double Doppler 4.0 — Atomic...

Double Doppler 4.0 — Atomic Swaps — Release NotesRelease Date: December 3rd, 2019TL;DR: Atomic Swaps Marketplace is here!Points to mentionAtomic Swaps is an advanced feature, currently in beta.DO NOT USE SWAPS FOR LARGE AMOUNTS OF MONEYFor Electrum use only Legacy seed type (we do not support Segwit)For Bitcoin use version Bitcoin Core v0.17.1For Litecoin use version Litecoin v0.17.1GeneralThe long-awaited Atomic Swaps Marketplace is here. We are happy to announce the release of Double Doppler 4.0 — our Desktop Wallet with Atomic Swaps.You can now publish offers and execute Beam<>BTC, Beam<>LTC and Beam<>QTUM swaps right from the Beam Wallet, in a fully decentralized manner, confidentially and without any counterparty risk.Download the latest version here.It is the first time when a privacy coin offers such a market place. For Beam, it is the first step towards a full-fledged DeFi ecosystem that we will be continuing to build in the months to come.Please see the detailed instructions on how to set up your wallet to start working with Atomic Swaps. If you are having issues, do not hesitate to contact us at our Support channel on Telegram or by email: support@beam.mwNote: The Atomic Swaps Marketplace is still in Beta, so use it at your own risk. We recommend transferring only small amounts.Official Release Notes are available on Github hereFeaturesDecentralized Atomic Swap Marketplace for BTC, LTC, and QTUMSupport connection to own node for BTC, LTC, and QTUMSupport conection with with Electrum for BTC, LTC, and QTUMAutomatic continues selection of fastest peers when connected to random nodeTransactions can be searched by a transaction ID, kernel ID, address, contact or commentImprovementsOur logo just became a pixel bit better, can you find the differences?Wallet approximate synchronization time is displayed nicely and much more accurately along with the remaining percentageCreating or restoring a wallet can be processed by a specific peerTransaction statuses are displayed in a nicer wayFixesAddress comment is now editableOver 200 tasks accomplished in total, for more details please see here: GitHub projectSupported PlatformsWindowsMacOSLinuxCome discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyDouble Doppler 4.0 — Atomic Swaps — Release Notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

19. 12. 04

Announcing the Beam Foundation

After over 18 months of living and working as a company, Beam is today announcing the first step towards decentralization — the official launch of the Beam Foundation.As we have stated from the get-go, while Beam started the project as a for-profit venture, our long-term goal always was to pass the control to a non-profit Foundation. This moment has now come.The Foundation will use the funds allocated to it in Beam Treasury in order to continue the development and promotion of Beam protocol and to advance the wider privacy-related agenda.Who and WhereThe Beam Foundation is registered in Singapore as a Company Limited by Guarantee — this the preferred way of registering a non-profit body in Singapore. We chose Singapore not only because it is crypto-friendly, but also because it is a truly global city, a place where East and West meet .The Foundation will be governed by a Board of up to 7 members. Initially, the Board will consist of four members. Here they are:Guy Corem — Professionally involved in the cryptocurrency industry since 2013, Guy co-founded and was the CEO of Spondoolies-Tech. In addition, Guy co-founded DAG Labs.Bo Dong — a veteran crypto trader/entrepreneur since 2016. Dong has a deep understanding in token economies and liquidity. Dong is the founder and CEO of Altonomy, a well-known liquidity provider in cryptocurrency space.Ferdous Bhai — highly-respected Bitcoin advocate, has established Canada’s largest Bitcoin OTC brokerage, YapCX, and started a high-performance cryptocurrency exchange, ChainRift. Ferdous is an acclaimed proponent of the Bitcoin’s peer-to-peer decentralized permissionless governance.Wilke Trei — a mathematician with specialization in computational discrete math and a freelancing mining software developer with a focus on memory-heavy algorithms that run on GPUs.All of the initial Board members served as advisors to Beam and have been supporting the project for quite some time now. They all have the best interests of the project in their heart.We are actively looking for 3 additional members to join the Board. In the future, the number of Board seats may be increased if the Directors decide so.In addition, Beam COO Amir Aaronson will be taking up the role of the COO of Beam Foundation, charged with operational aspects of the work.The Foundation website is available here: www.beam-foundation.orgThe FundsAs stated in our Emission Schedule, the Beam Foundation is endowed with 20% of the Treasury, i.e. 4% of total coins emitted in the first 5 years of existence of the protocol. The total number of Foundation coins over the 5 years stands at 6,307,200 Beam.In January 2019, we performed a forward sale of 1 million of Foundation tokens at $1 per token. That was done as a hedging move. As all other investors, the investors participating in the forward sale will be receiving their coins in monthly installments over the course of five years.Initially, a large part of the development will be done by the Beam Core Group. In the future, the Foundation will also be launching a community portal to allow anyone to submit requests for funding.Besides development, the Foundation will also support global awareness and business development for Beam, as well as a wider privacy agenda.GovernanceThe Governance of the Foundation will be performed by the Board, and all the decisions will be taken by a simple majority of votes.In the future, the Foundation will strive to change the decision making to be more distributed by creating a DAO-like governance system. This is not in the immediate plans however.The Beam Core GroupIn the coming months, the Beam Company will be transforming into Beam Core Group. Beam Core Group will be the development arm of the Beam Foundation.Beam Core Group will continue to work on the previously announced roadmap and to deliver on the Beam vision. We are committed to the same high standards of engineering and research that we were following until now.It is our goal that with time, more and more independent developers start working on Beam. We expect however that in the first 6–12 months of the existence of the Foundation, most of the work will be done by the Beam Core Group.As the Beam Company transforms into a more loosely organized Beam Core Group, the roles of the original executive team may be shifting — we will be updating the community as it happens.TransparencyThe Beam Foundation will be providing financial reports of its activity. Those reports will be published on the Foundation website, along with other information.Our goal is to be as transparent as possible.Into the futureSetting up the Beam Foundation and establishing an independent Board is an important step towards further decentralization of Beam. It is of course just the first step — in the coming years, the Foundation’s will work to build a fully decentralized global community that will continue to contribute to Beam and that will make Beam development and maintenance fully decentralized and resilient.Come discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyAnnouncing the Beam Foundation was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

19. 11. 25

Why “Breaking Mimblewimble’...

TL;DR: The “Breaking Mimblewimble Privacy Model” attack will not be effective on Beam — Beam’s decoy outputs make it much harder to build the transaction graph. Upcoming Lelantus-MW will make building the transaction graph virtually impossible even against more sophisticated attacks.We would like to give our feedback on the article recently published by Ivan Bogatyy, claiming that there is no privacy in Mimblewimble. The article made some waves, and we would like to thank Ivan for his work and research.However, we believe that some members of our community were needlessly concerned, so we want to address the presented issues — which were known and discussed in depth in the past — and explain how Beam already mitigates them.What does the attack actually doThe system Ivan built collects logs from several “sniffer” nodes connected to the Grin network, and analyzes them.When analyzing the logs, the author is looking for transactions that have only one kernel. In Grin, having one kernel indicates that a transaction was not merged with any other transactions, and thus the inputs of this transaction are linked to its outputs. With enough such links, it is possible to build a transaction graph that connects between different wallets and use this graph, for instance, to prove a financial connection between two known parties.Ivan’s work does not actually build a transaction graph, it demonstrates that building such graph may be possible — there is quite a long way from finding linked inputs and outputs to building the actual transaction graph to actually establishing a link between specific peers.The attack also does not reveal any user identities such as IP address, neither does it reveal the amounts transacted.Why does it work in GrinThe reason for a large amount of such one-kernel transactions being broadcast to the network is that Grin network is not saturated and there are not enough transactions to be merged in the stem phase of Dandelion protocol.As the usage grows, the anonymity will improve, but currently, as Ivan has shown it, the anonymity set is very low.How Beam is differentWhile based on the same Mimblewimble protocol, Beam’s implementation of Dandelion has an important privacy improvement over Grin’s.Early on in the project we identified the potential transaction linkability in Mimblewimble and thought about ways to mitigate it.Already in September 2018 Valdo published a technical paper on transaction linkability and how Beam is tackling it. The paper describes the concept of decoy (aka Dummy) UTXOs. Note that the feature was implemented in Beam before mainnet launch and the mechanism was discussed with Grin’s devs, which decided not to implement it.How do those dummies work? At every step of the Dandelion Stem Phase, Beam nodes check whether the merged transactions (might be only one transaction) have at least 5 outputs.If not, decoy outputs are added to the merged transactions, making sure that the number of outputs is at least 5.You can view Beam blockchain explorers here or here and see that every block that has at least 2 kernels (meaning blocks that has at least one transaction which isn’t coinbase only) has at least 7 outputs (coinbase, fee, payee’s, 4 dummies).Each one of the dummy outputs has a value of zero, but it is completely indistinguishable from regular outputs — all outputs look like random numbers.At a later stage (a randomly chosen block height for each output), the node adds dummy UTXOs as inputs to a random transaction, most likely belonging to a different user, thus spending them and removing them from the blockchain, but also creating a relation between users that are in fact unrelated. Hence the “decoys” name.It’s important to note that since those decoy outputs are eventually spent, the mechanism doesn’t create any permanent clutter on the blockchain.Why the attack will be much harder to implement on Beam?If a similar exercise were to be run on Beam, the researcher would probably still find a lot of transactions with a single kernel. While Beam network processes about 60% more transactions than Grin (averaged over the past 30 days), it is still not enough to guarantee that two or more real transactions “meet” always while in the Stem phase. However, because of the dummy outputs, such single-kernel transactions will not be useful for discovery of the transaction graph.Decoys in Beam make building the transaction graph a probabilistic task, with the probability of a link between two wallets decaying exponentially with the growth of the number of hops.As Ivan wrote in his explanatory tweet:https://twitter.com/IvanBogatyy/status/1196441085221855233?s=20It would not be true for Beam — even if transactions are not aggregated with others, they still have an anonymity set of at least 4 decoy outputs (it’s a configurable number).Next step: Lelantus-MWDecoy outputs in Beam increase the anonymity set, and make building a transaction graph using a technique described by Ivan much harder, but still possible to some extent. Other more sophisticated active attacks were also described by others, like Ian Miers’s flashlight attack.Therefore, we implemented Lelantus-MW and will activate it soon.Lelantus-MW will dramatically increase the anonymity set (100K outputs) and will make it almost impossible to build the transactions graph if the user chose to use Lelantus-mw transactions from time to time.Read more about Lelantus-MW here and here.And it ends with a challengeWe would like to challenge Ivan to perform an analysis on the Beam network to try to establish provable links between a meaningful number of wallets. Finding transactions with one kernel won’t really work here.Come discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyWhy “Breaking Mimblewimble’s Privacy Model” will not work with Beam was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

19. 11. 19

UX++ for Beam Wallet (part 2)

A while ago when we’ve started to think about how to improve and redesign our mobile wallet (see Part 1 here) it became clear that one step won’t make the whole story. In the previous release, we’ve added a lot of new functionality (e.g. finer control over addresses, search, address categories, etc). In the current release, we bring 3 big things under your fingerprints:Funds restore from a seed phrase: that’s right, you can restore any wallet given that you have the seed phrase kept somewhere. This fairly complicated and highly anticipated feature is available now and we dare to ask those who gave a lower score to the app to play with the app and to do the right thing ;)Many screens since the previous release were redesigned (see below). Brand fresh touch will bring the eye-pleasing info in a more structured and more functional way.Languages (our community effort) the wallet is closer to the way of your thinking :) The challenges of this adventure and the names of the heroes participating will be covered in a separate article (stay tuned).So, let’s see what’s in the box.☀️ Features (UX/UI and more)Mobile restore came to town: no need to switch to the desktop and to transfer the funds back anymore. You can restore from the generic node in the cloud or from a specific node you trust!We want the app to be as stable and as robust as possible. To achieve that, we’d like to ask you to submit technical details when a crash occurs. However, as a confidential wallet that prides privacy, we’ll ask you very politely each time before trying to submit that kind of info. Since the info is sent, we obviously won’t collect any information in the background.Transactions and transaction details screens were redesigned to match the new style.Addresses and address details screens were redesigned. Categories are now called “tags” and a single address can be denoted by several tags from now on.The redesigned UTXO and UTXO details screens display the list of transactions for every UTXO.Payment proof screens were redesigned.Did you ever capture a screenshot to send the transaction details to the sender? Well, we’ve thought about a more stylish way to achieve the purpose, we’ve called it “Share transaction details”.Some customers suggested scanning the QR code from a photo, taken once and kept in the library. All you needed to do was to ask for it :)👍 ImprovementsSmaller things we couldn’t leave behind:Since we value your every tap, some textual fields provide a nice way to reset the value with a single click (on iOS).On receive and send screens addresses are copiable with a long tap.Transactions can be searched by Kernel ID.Loading bar works smoother and is a bit more informativeOnline status works better when a phone is disconnected from the InternetShow Owner Key flow became much more informativeOn Android, the app doesn’t need to be restarted when a language is changedOn Android, the app responsivity became much faster and usage feel became smoother due to significant architectural reworkThere’s much more to tell as the iOS sprints (2 in total) counted 80+ issues and Android sprints (2 in total) counted 100+ issues. Many fixes of typos, explanatory messages, elements placements, colors — all to make the app more eye-pleasing and more intuitive to use. We could add more details here but your time is precious and we’re happy with fewer details and more “it just works” feeling.🍳 What’s cookingLuckily, there is always something that keeps us busy:Android version that supports the same features set is in the works as I type.We are considering to make addresses even more usable. We realize that in Mimblewimble the same person usually has many addresses (some of them were created to be used only once). We are aware of that and need to brainstorm on that a bit.More BIG features are coming, but it’s a bit too early to elaborate. Hint: follow our desktop projects.🗣 Calls to actions!!!Please rate our app in the App Store or in Play Store or revise your lower score (if given before) in case you think the current version suits your expectations better.Let us know what do you think. You know where to find us. We take pride in what we do yet we are eager to hear how we can do even better.Use Beam: probably the most usable wallet for the Mimblewimble-based privacy coin!Confidentially yours, Beam Product, Development and QA teamsCome discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyUX++ for Beam Wallet (part 2) was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

19. 10. 30

Clear Cathode 3.1, iOS — Re...

Clear Cathode 3.1, iOS — Release NotesRelease Date: October 29th, 2019GeneralRelease notesSupported PlatformsAll devices running iOS 11.0 and higherFeaturesWhen a crash occurs we’ll ask politely to submit the technical details, that will allow us to investigate the issue and improve app’s stabilityTransactions screen was introduced to present the extended transactions infoImprovementsLoading bar works smoother and is a bit more informativePayment proof screen, settings screens, transaction details screen, tag edit screen, main menu, transaction statuses and icons updated to match the new designShow owner key flow became more informativeTransaction actions can be triggered through haptic touch / 3d touchFixesMany fixes of typos, explanatory messages, elements placements, colors — all to make the app more eye-pleasing and more intuitive to use.Known limitationsWhen restoring your funds in automatic mode, verify that your most recent transaction (from any device) was completed at least 1 hour ago. Otherwise, your restored balance may be incorrect and additional restore procedure will be required.When restoring your funds with your specific node, verify that the node is fully synchronized with the blockchain before starting the restore procedure. Otherwise, your restored balance may be incorrect and additional restore procedure will be required.Points to mentionDO NOT SIMULTANEOUSLY RUN TWO WALLETS INITIATED FROM THE SAME SEED PHRASE. No funds will be lost in any case, please read this article for full details.If you really want to run two wallets (read: geek mode), initiated from the same seed phrase, make sure each wallet is connected to the node configured with the owner key (which is derived from the seed phrase).Even if two wallets are connected with such a node which is properly configured with the owner key, the transaction history will not be syncronized among them (each wallet will see the correct balance but only its own transaction history).Come discover Beam and join our community!Download Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyClear Cathode 3.1, iOS — Release Notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

19. 10. 30

How to install Beam on your...

Tutorial — How to install Beam on your Raspberry PiPrefaceIn my last medium article, I described the benefits in privacy and usability to run an own Beam network node over trusting an external partner and how to realize an own node on a free google cloud instance. While this is an amazing opportunity to strengthen the Beam network and to improve your wallet experience with an always-online wallet, this still requires to use external commercial services to realize it. Therefore this second article about running an own Beam node covers how to make it work on one of the most prevalent and affordable hardware platforms available: a Raspberry Pi. Besides the benefits of running an own command line wallet and node, the article also will cover how to build and install the graphical wallet. Having this the user experience for Beam on your Raspberry is just as amazing as on a standard desktop computer.This tutorial will assume you are running a Raspberry Pi 3 or 4 with current Raspbian Duster (in my case concretely version dated 2019–09–26). Also, we need to ensure our SD card has at least 16 GByte (better 32), so the operating system, build tools as well as the blockchain fit to it. Thanks to the good scalability of a Mimblewimble blockchain we can expect a clean Raspbian and the Beam blockchain may fit a 16 GByte SD card for at least another year, maybe two.PreparationsThe nature of Beam transaction building process requires that the clock of the computer a wallet runs on needs to be at least roughly correct. Since a Raspberry Pi has no integrated real-time clock please make sure that this is the case for your device before you start running a Beam wallet on it. There are plenty of opportunities to ensure that, e.g. adding a separate real-time clock or a GPS module to your Pi. But also the pure software solutions are sufficient — in case your firewall does not block the time server ports it is likely that the clock will in fact work correct shortly after reboot. Describing different ways on how to ensure it is beyond the scope of this article.Furthermore, during the build there are some libraries of Beam that require a higher than the standard amount of RAM when building. To cover this we should increase the virtual memory available to Raspbian. In case you own the 4G version of the Raspberry Pi 4 you can skip this step. Open the terminal on your Raspbian and type in:sudo geany /etc/dphys-swapfileA text editor will pop up. Edit the number inline 16 to 2048, then store and close the editor. Afterward, typesudo dphys-swapfile setupinto the command line. Note that this will occupy two GByte of memory on your SD card. After all building work is done you can use the two commandssudo dphys-swapfile swapoffsudo dphys-swapfile uninstallto disable the swap file again. Ideally, you afterward change the size back to the system default and activate it by invoking “setup” again.How to Build the CLI Node and WalletWe will start by installing the required dependencies of Beam by copy-pasting the following four lines to the command line, line by line and confirm each with the return key.sudo apt-get install gitsudo apt-get install cmakesudo apt-get install libboost-all-devsudo apt-get install opensslNow we already have the dependencies of Beam on our Raspberry Pi, except for the GUI wallet that will be handled later. Next, we will download the Beam source code and change to the right branch of Beam to get a build that can connect to the Beam main network.git clone https://github.com/BeamMW/beam.gitcd beamgit checkout mainnetNow we are ready to run the compilation.In case you want to build the gui wallet as well skip this step and scroll down to the section describing the gui wallet build. You then can resume after this step.For this, you need to copy the following line to your command line. Note that the parameter after the “-j” is giving the number of threads to be used for building. In case you run a Raspberry Pi 4B with 4GByte of RAM you may choose “-j 4” to use all four processor cores for building. For the 2G RAM version “-j 3” is optimal, while a Raspberry Pi 4 1G or Raspberry Pi 4 should use “-j 2” or even “-j 1”. The rationale is that compiling slows down if RAM is exhausted and the swap file needs to be used.cmake -DBEAM_NO_QT_UI_WALLET=1 -DARCH_NATIVE=1 . && make -j 3On the 2G model using -j 3 is very smooth except for a handful of libraries around 65% of the build process where the swap file is used. Overall building beam as a whole requires about half an hour on a Raspberry Pi 4 with 2G RAM — plenty of time for a long coffee break.When done we built the following executables:./beam/beam-node./wallet/beam-walletthat we can copy to a common folder and use them as described in the Beam documentation or in my previous article about Beam on a cloud VM instance. Note that the initial synchronization of the node will take some hours, although it is quicker than the cloud instance. For the source version at the time of writing, I highly recommend activating the cut-through and fast-sync with the “horizon_hi” and “horizon_lo” parameter as described in the cloud computing article. Otherwise, the Beam blockchain may occupy too much space on your Raspberry Pi SD card.How to Install the CLI Node and Setup AutostartIn case that you want to clean the build directory to save some space on your Pi it may make sense to install the Beam node and the CLI wallet in another directory and add this to the system search path. Of course, you also can copy it manually and use it as described in my cloud vm article.Use the following lines to create a new directory for your beam stuff in your home directory and copy the relevant files over to this directory.sudo mkdir -p opt/beamsudo chown pi:pi opt/beam cp ~/beam/{beam/beam-node,wallet/beam-wallet} /opt/beamBesides the executables, we will also create a directory for the configuration files and the node data within our home directory.mkdir -p ~/.local/share/beamcp ~/beam/{beam/beam-node.cfg,wallet/beam-wallet.cfg} ~/.local/share/beamThe relevant files are now copied to the new directory and you can clean up the sources — unless you want to build the GUI wallet as well (see below!).Now we will tell the system about the new locations of the executables as well as the configurations. Typegeany /home/pi/.bashrcand scroll down the file. At the bottom add the following lines:export PATH=/opt/beam:$PATHfunction BeamNode {pushd ~/.local/share/beambeam-node $@popd}function BeamCLIWallet {pushd ~/.local/share/beambeam-node $@popd}Close the text editor and typesource ./.bashrcNow — and whenever you open your console later — your system will know the two commands “BeamNode” and “BeamCLIWallet” and switch to the right working directories automatically — and come back to your current working directory when done. The corresponding configuration files for your node can be accessed by typinggeany /home/pi/.local/share/beam/beam-node.cfgfor the node configuration. To run the node in a very basic configuration its needed to change just two lines. First head out for line 25, which is# peer=and change it topeer=eu-nodes.mainnet.beam.mw:8100You also can pick any other Beam node to start your sync with. A list with known and trusted nodes can be found here.Furthermore to enable fast syncing — which saves space and CPU time on your Raspberry-Pi add the linefast_sync=1to the bottom of the file. Then you already could start your node and strengthen the Beam network. Other options are only required in case you want to connect your own wallet or want to solo mine with your node.Configure your node for your needs and type in “BeamNode” to start it for its first sync. This will take several hours and also will put a lot of load to the CPU. Best do this overnight but do not worry: once the node is fully synced the system load of the running node is almost zero.Still not enough? It would be cool to start the node on each reboot in the background to keep it always on and synced, right? Ok, let’s do so!For this task, we will install tmux that allows us to start a console program on boot-up and get the command line to front in case we need it.sudo apt-get install tmuxOnce this is done we will create a cron job that will launch our beam node on each boot-up. Type ingeany /opt/beam/beam.cronto open the text editor and copy in the following lines.#!/bin/bashsleep 5/usr/bin/tmux new-session -d -s beamSession ‘/bin/bash’/usr/bin/tmux send-keys -t beamSession “source /home/pi/.bashrc” C-m/usr/bin/tmux send-keys -t beamSession “BeamNode” C-mSave the file and close the editor. Note that we did set a sleep time of 5 seconds before the node is supposed to start after reboot. This is to allow the system to establish the network connection first. Also starting multiple tmux instances at the same time may cause problems, so if you want to start multiple programs (e.g. a CLI wallet) by this method I recommend to set different sleeping times.Now we will make cron aware of this file. Type incrontab -eIn case you never did so till now you will be asked a question about the editor to use. Hit 1, so nano will be used.Navigate with the arrow keys to the bottom of the file and insert the following line@reboot /opt/beam/beam.cronThen hit ctrl+o to save the file and crtl+x to close the editor. Now on every boot, the system will start your beam node in a separate session. When you open the command line you can see the running session by typingtmux attach-session -t beamSessionDo this on your first reboot to ensure everything is working. If not it is likely that some aspects are missing in the configuration file — I assume that the node is completely configured by this file and does not require additional command line parameters.How to Build and Install the GUI WalletIn order to build the beam GUI wallet, we will need to install some additional dependencies that are used by the graphical interface of the wallet. This can be done by copying the following four lines to your command line.sudo apt-get install qt5-defaultsudo apt-get install qtdeclarative5-dev libqt5svg5-dev sudo apt-get install qttools5-dev-tools qttools5-devsudo apt-get install qml-module-qtquick-controls qml-module-qtquick-controls2The installation of these dependencies will require approximately 200 MByte extra space on your SD card. Once done we can start the build of the beam GUI wallet. Note that in case you have not built yet the node itself this will do it. In case you already have built it, it may be required to typerm ./CMakeCache.txtbefore the build, so the building system notices the changes.To start the actual build type incmake -DARCH_NATIVE=1 . && make -j 3You may again customize the -j parameter to the specs of your Raspberry Pi as described in the section about the node build process.Once the build is done we will copy the beam GUI wallet executable to a different location — so we are able to clean up the build space afterward — and create a menu entry for it.Type insudo mkdir -p /opt/beamsudo cp ./ui/BeamWallet /opt/beamsudo cp ./ui/icons/beam_mainnet.png /usr/share/pixmaps/sudo geany /usr/share/applications/BeamWallet.desktopand a text editor will open up. Copy the following lines into the empty open file and store it.[Desktop Entry]Name=Beam WalletComment=GUI Wallet for BEAM MW MainnetIcon=/usr/share/pixmaps/beam_mainnet.pngExec=/opt/beam/BeamWalletType=ApplicationEncoding=UTF-8Terminal=falseCategories=Network;Now on the next reboot or after typing inlxpanelctl restartyou will be able to see the shortcut for your beam gui wallet in the network menu of your Raspbian. The usage is exactly as used from other Linux based systems.Enjoy using Beam on your Raspberry Pi! In case you liked this article leave me a clap or a small donation on my Beam donation address. Thank you for reading!2346a827cb56ca74e34680593e50d7b1fa4a169332415a1d5984c6f874395c3684bCome discover Beam and join our community!Download Beam Desktop Wallet hereDownload Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyHow to install Beam on your Raspberry Pi was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

19. 10. 17

Clear Cathode 3.2, Android ...

Clear Cathode 3.2, Android — Release NotesRelease Date: October 16th, 2019General NotesRelease NotesFeaturesThe app responsivity became much faster and usage feel became smoother due to significant architectural reworkTransaction details screen, address/contact details screen, tag create/update screen, payment proof screens were redesignedTransactions history can be exported and saved on the deviceOn the transaction screen, multiple transactions can be selectedImprovementsTransactions can be searched by Kernel ID (from the Transactions screen)Loading bar works smoother and is a bit more informativeWhen a crash occurs we’ll ask politely to submit the technical details, that will allow us to investigate the issue and improve app’s stabilityWhen changing the language the app doesn’t need to be restarted anymoreFixesMany fixes of typos, explanatory messages, elements placements, colors — all to make the app more eye-pleasing and more intuitive to useKnown limitationsWhen restoring your funds in automatic mode, verify that your most recent transaction (from any device) was completed at least 1 hour ago. Otherwise, your restored balance may be incorrect and additional restore procedure will be requiredWhen restoring your funds with your specific node, verify that the node is fully synchronized with the blockchain before starting the restore procedure. Otherwise, your restored balance may be incorrect and additional restore procedure will be requiredPoints to mentionDO NOT SIMULTANEOUSLY RUN TWO WALLETS INITIATED FROM THE SAME SEED PHRASE. No funds will be lost in any case, please read this article for full detailsIf you really want to run two wallets (read: geek mode), initiated from the same seed phrase, make sure each wallet is connected to the node configured with the owner key (which is derived from the seed phrase)Even if two wallets are connected with such a node which is properly configured with the owner key, the transaction history will not be syncronized among them (each wallet will see the correct balance but only its own transaction history)Come discover Beam and join our community!Download Beam iOS Wallet on App StoreDownload Beam Android Wallet on Google PlayLearn more about Beam on our website and blogTelegram: t.me/BeamPrivacyQQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4Reddit: reddit.com/r/beamprivacy/Twitter: twitter.com/beamprivacyClear Cathode 3.2, Android — Release Notes was originally published in BEAM-MW on Medium, where people are continuing the conversation by highlighting and responding to this story.

BEAM

19. 10. 16

Transaction History
Transaction History Address
BitForex Short cut
Hotbit Short cut
DragonEx Short cut
MXC Short cut
BigONE Short cut
Security verification

There is security verification of the project
Why security verification is necessary?

Read more

comment

* Written questions can not be edited.

* The questions will be answered directly by the token team.

Information
Platform ERC20
Accepting
Hard cap -
Audit -
Stage -
Location -