|
Distribution of bytes is finished, 110,411.089425997 GB distributed. New available supply is 365,903.008377294 GB. It is already updated on coinmarketcap.
Distribution of blackbytes will start in a few hours and will take much longer, likely more than 1 day. I'll post when it is done.
|
|
|
|
@tonych, Hi, recently I did a BB transaction via light client, v 1.9.0. As it was expected the remaining fund (f=f1+f2) has been split between two addresses i.e ADDR1 (f1) and ADDR2(f2). I have decided to consolidate all of it on ADDR1, but after choose "Send all" option and click "Send" nothing happened in sense that fund again was split between ADDR1 (f1) and ADDR2(f2). I have repeated the same once more but the result was exactly similar. So I look on transaction and found that it was that really happened ADDR(f1) ==> ADDR(f1) (transaction) and ADDR(f2) = ADDR2(f2) (which means no transaction). Then I did the following : choose Amount, put into Amount field f1 + f2 (in fact a bit smaller to take into account the fee), choose ADDR1 and Send. With this procedure I have finally got ADDR1 (f1+f2). So conclusion: the "Send all" does not function properly in v 1.9.0. With previous client's version there was no such problem
Fixed in 1.9.1 |
|
|
|
Version 1.9.1 released https://github.com/byteball/byteball/releases* Android app now displays balance almost immediately after starting * Hide balance before the password is entered when starting a password-protected wallet * Bugfix: smart wallets created based on other smart wallets are now visible * Bugfix: when using "Send all" sometimes the wallet was sending only part of the balance * Bugfix: sync could become stalled if sending a new transaction while still syncing * Additional checks to prevent creation of unspendable addresses which occasionally happened on some Android devices * Ability to re-send private payloads to other co-signers on multisig wallets * Ability to delete multisig wallet whose creation was not finished * Sync progress is now displayed as date (percentages caused confusion for many users) * Multiple UI improvements * Multiple small bugfixes * Small performance improvement * Improved translations Special thanks to @CorePrime95 for multiple UI improvements and bugfixes. |
|
|
|
Distribution of bytes was finished several hours ago.
Total distributed: 66,208.049453060 GB.
New circulating supply: 255,491.918951297 GB (already updated on coinmarketcap).
The distributed amount is worth $47m at the current price.
Distribution of blackbytes is still under way, I'll post when it is finished.
Distribution of blackbytes is now finished too. 127,513.125794221 GBB distributed 12,258.687406134 GBB added to the community fund https://docs.google.com/spreadsheets/d/1foYdri-vadnq8Kbr51QVhBlXiswHtiDpaShVaWO060sThe next distribution is scheduled for the full moon of July: July 9, 2017 at 04:07 UTC, the rules stay the same: BTC to bytes: 1 BTC of proven balance gives you 62.5 MB (0.0625 GB) BTC to blackbytes: 1 BTC of proven balance gives you 2.1111 * 62.5 million blackbytes (money supply of blackbytes is 2.1111 times more than that of bytes) Bytes to bytes: 1 byte on any Byteball address gives you 0.2 new bytes Bytes to blackbytes: 1 byte on linked Byteball address gives you 0.42222 blackbytes Putting this another way, to receive 1 GB from the distribution, you need to already hold 16 BTC or 5 GB. These same holdings also give you 2.1111 GBB (giga-blackbyte). |
|
|
|
|
Distribution of bytes was finished several hours ago.
Total distributed: 66,208.049453060 GB.
New circulating supply: 255,491.918951297 GB (already updated on coinmarketcap).
The distributed amount is worth $47m at the current price.
Distribution of blackbytes is still under way, I'll post when it is finished.
|
|
|
|
After a lot of hard work, the transition bot will now take some rest  It's seat will be taken by the distribution bot. P.S. You can now safely move your bytes and BTC out of the linked addresses. |
|
|
|
I asked this on slack but would like to ask again here:
Tony, how do you see whales and exchanges linking wallets to get free Gbytes?
Many greedy xchange operators will use Gbyte to just make more money by linking wallets of own exhanges.
What about whales? Last give away we seen nearly 200k btc linked. i seen myself few position 100btc + like one after another. Do you have mechanism to recognise wallets of exchange? If so are you still allowing to receive free bytes?
We are filtering the exchange addresses when their customers (not the exchanges themselves) try to link them by doing a withdrawal. This is considered cheating. I am not aware of any exchanges that had covertly linked their BTC wallets (Cryptox linked openly, and distributed among its users). If you find one, please let its customers know. No issues with whales, the rules are the same for everybody irrespective of wealth. |
|
|
|
Compile windows client, and got this error:
C:\Byteball\byteball>grunt inno64
Running "innosetup_compiler:win64" (innosetup_compiler) task
Error in C:\Byteball\byteball\webkitbuilds\setup-win64.iss: The system cannot find the path specified.
Compile aborted.
It's difficult to troubleshoot without seeing your system. There are several file paths mentioned in this file: OutputDir=../../byteballbuilds ..\..\byteballbuilds\{#MyAppPackageName}\win64 ../public/img/icons/icon-white-outline.ico Make sure they all exist. Not an issue. |
|
|
|
Improved Polish translation didn't make it from Crowdin into the release. Any dope why?   The language codes were changed to the standard ones (e.g. from pl to pl_PL), please choose Polish in your wallet's language settings again and you will see the new translations. |
|
|
|
Thanks for all new translations, our localization is improving very fast! For some languages, proofreaders were assigned (you got an email if you were assigned), proofreaders need to approve the translations. is possible to add romanian translation aswell? 2 countries from Europe have national language as romanian. *(Romania and Rep. of Moldova.)
Romanian added. Does Hindi language available?
Hindi added. |
|
|
|
why to make new assets?
ICOs, shares, bonds, fiat-pegged coins, loyalty points, minutes of airtime, assets in online games, whatever you can imagine how would they be traded ? and where?
They can be immediately traded P2P via smart contracts (same as blackbytes). Also we have a trustless exchange already prepared https://github.com/byteball/byteball-exchange but not started yet. |
|
|
|
|
Inspired by my conversation with Aleš Janda (who is very knowledgeable in blockchain analysis and runs walletexplorer.com and chainalysis.com), there is a new rule for microtransaction-proven bitcoin addresses:
- if the address had more than 50 transactions in the last 3 days, it is rejected. Linking by signature is still possible.
Such frequent transactions are common for exchanges and other shared wallets, and the rule prevents its customers from linking the shared address by doing a withdrawal.
This adds to the other two rules that serve the same purpose:
- if the microtransaction has more than 2 outputs, it is rejected (with the exception of Electrum 2fa transactions that have 3 outputs), because exchanges often aggregate several withdrawals into a single transaction
- if the same address was already linked before by another user, the new link is rejected and the old link is canceled. This applies only to tx-proven addresses, and the reason for this rule is that for sufficiently popular exchanges, there will likely be more than one user who tries to cheat.
The two old rules were good enough at filtering large well known exchanges but a small number of addresses of smaller exchanges were still linked. The new rule is to filter them too.
|
|
|
|
Now it got easier to translate Byteball wallet into your language. Join Crowdin and translate small text fragments in user friendly interface at https://crowdin.com/project/byteball (Crowdin is free for open source projects like Byteball).  |
|
|
|
|
Show Posts
