Version 1.5 released https://github.com/byteball/byteball/releasesIt's the biggest update since the launch. It enables conditional payments, which allow you to P2P exchange bytes vs blackbytes since today. Much more in the next releases. Read my Medium article about making P2P great again https://medium.com/byteball/making-p2p-great-again-fe9e20546a4a#.i6kj1ug99Note that to bind your payment to a condition you must be connected in chat with the payee and click his address or accept a payment request. Other updates in this release: * Fixed frequent disconnects that might affect sync speed * Small performance optimizations * Multiple small bugs fixed Please upgrade. The wallet might start a bit longer than usual the first time after the upgrade, this is because it needs to upgrade the database, be patient. Be prepared for bugs since it is a big update (I guess you are already used to expecting this when you are into something new). |
|
|
|
Reinstalled Byteball.
I am trying to run a program with the old directory (where the wallet is located) and get:
"Error Uncaught exception: Error: wallet not found
is change = 0, index = 0"
Did you move/copy/replace any files in the app's data folder? |
|
|
|
What happens if all 12 witnesses fell under DDoS attack? Will network stuck?
Their IP addresses are not publicly known, so it is not easy to learn what to attack in the first place. Even if DDoSed, a witness can quickly move to a new IP. |
|
|
|
Version 1.4 released https://github.com/byteball/byteball/releasesIt includes: * Full backup and restore. The backup file is compressed, encrypted, and compatible with all platforms * Improved speed of sync * Multiple bugfixes Please upgrade. Android version is already in Google Play. If you plan to move your wallet to another device using backup/restore, please close the wallet and don't use it on the first device after creating the backup. Overlapped use of the same keys on multiple devices can lead to multiple issues such as non-delivered blackbytes and lost chat messages. If what you want is access to the same money from multiple devices, use multisig instead. I have plans to move my wallet to another device. Do I need to complete a full sync on the new device before restoring from full backup? No, you don't, you can move it half-synced. The PC I'm moving my wallet to has never had any version of byteball software, so I'm syncing from scratch. It took about 12 hours to get to 69% and then it was stuck on 69% for about five hours. At this point, I closed the wallet and re-opened to see if it would help get me over this 69% hump. The wallet is back at 69% and it's been stuck for approximately six hours. Is this normal for a new install? The PC I've been using since the initial 12/25 distro never became stuck at any point while syncing. Although, I was opening my wallet daily, since 12/25, so it may have never got stuck because I was syncing regularly. Any insight would be appreciated  This is not normal. Your cpu and disk usage should normally be high during sync. If it is not, something is wrong, a restart usually helps. You don't need to sync the 2nd PC before moving. As far as I understand, you already have a fully synced wallet on the 1st PC and since you are doing full backup that contains the entire database, you'll get a fully synced wallet after restore. The old data on the 2nd PC will be deleted during restore anyway. |
|
|
|
Version 1.4 released https://github.com/byteball/byteball/releasesIt includes: * Full backup and restore. The backup file is compressed, encrypted, and compatible with all platforms * Improved speed of sync * Multiple bugfixes Please upgrade. Android version is already in Google Play. If you plan to move your wallet to another device using backup/restore, please close the wallet and don't use it on the first device after creating the backup. Overlapped use of the same keys on multiple devices can lead to multiple issues such as non-delivered blackbytes and lost chat messages. If what you want is access to the same money from multiple devices, use multisig instead. I have plans to move my wallet to another device. Do I need to complete a full sync on the new device before restoring from full backup? No, you don't, you can move it half-synced. |
|
|
|
https://bitcointalk.org/index.php?topic=1799665.msg17950428#msg17950428....When I discussed this in the Byteball thread, the Byteball author Anthony realized there is a problem and started to talk about avoidance of needing to replace witnesses and how to have a community wide vote and other mechanisms for overcoming the inherent flaw (which means really he will end up needing whales same as for DPoS to avoid chaos so then you are right back to centralization and the failure of Bitshares and Steem again).....@tonych  False statement. |
|
|
|
Version 1.4 released https://github.com/byteball/byteball/releasesIt includes: * Full backup and restore. The backup file is compressed, encrypted, and compatible with all platforms * Improved speed of sync * Multiple bugfixes  Please upgrade. Android version is already in Google Play. If you plan to move your wallet to another device using backup/restore, please close the wallet and don't use it on the first device after creating the backup. Overlapped use of the same keys on multiple devices can lead to multiple issues such as non-delivered blackbytes and lost chat messages. If what you want is access to the same money from multiple devices, use multisig instead. |
|
|
|
I can not find in application folder
conf.json to change client from full to lite.
Where is the configuration file can be found in Windows XP
When you say application folder, do you mean %LOCALAPPDATA%\byteball? That's where you should try looking. Having said that, you can not change a client from full to light and vice-versa. You have to reinstall and chose light. When I tried to reinstall... I've got error:  System: Windows XP 64 bit. I can provide the necessary logs. XP is not supported, 7 is minimum. |
|
|
|
Does adding more byteball-hubs help the network process more transactions? Does a byteball-relay also help, but just doesnt store temporarily any private-messages like a hub does?
Just a little bit, as much as it helps distribute the load created by catching up nodes. What the hub/relay are more useful for is their help in propagation of new transactions and in reliability. |
|
|
|
Why is Byteball called Byte on Bitsquare and not Byteball?
Byteball is a platform, Bytes is a currency. Same as Ethereum/Ether. |
|
|
|
can anybody tell about TPS rate and predictable database growth?
There is no TPS set in stone as with bitcoin, where the blocksize basically determines how many transactions you can fit in a block, with Byteball, theoretically it should handle hundreds of thousands tx/s, but today its not optimized at all for this speed. Correct. I guess the upper practical limit is the 12 witnesses, how many transactions they can see (bot dont need to see it at the same time) and post to each other and append to the database, to the main chain.
Wrong. Witnesses don't do any more work than any other full node, they are not special with respect to TPS, and they are not a limiting factor in any way. There is nothing stopping you from making really a massive amounts of transactions on your own chain - and have it merged to the Main Chain when posting it for the witnesses to see. As long as you didnt double-spend, the verification of which witnesses do takes little time compared to what you spend in making the transactions, if all is fine, your chain of massive amount of txs will be in the main chain.
Again, this implies that it is witnesses who are doing verification and detect double-spends. Wrong - every full node does it in exactly the same way. We use witnesses only to establish order of events by looking back in history. |
|
|
|
That's a valid concern and freezal got it right: the network had to start centralized and no one's showed up yet with the needed reputation and credibility. I'm going to use every opportunity to relinquish control over 11 out of 12 witnesses in favor of reputable individuals/organizations/companies that are willing to be part of the network. That would make the network only stronger thanks to both their involvement and the network becoming more decentralized.
Thanks for clarifying that. The other concern that keeps coming to my mind is this: what happens if 2 or more of the 12 witnesses goes down (offline) for various reasons (hardware mulfunction, operator not interested in running it anymore, government seizure etc.). Will this cause any network disruption? If yes, what kind of disruptions would that be? As long as the majority (7 out of 12) of witnesses are online and behave honestly, the network is healthy. |
|
|
|
If by "centralized 'mechanism'" you mean the fact that tonych control all 12 witnesses I'd say I don't think the mechanism of changing witnesses is somehow deactivate 'till the distribution is over.
I think it's in full blow validity and someone who present a very compelling argument to be one of the twelve witnesses could assume the role.
Now, tonych may have any number of reasons to be in this role, but one would be: the network had to start securely somewhere, and the other being: no one's showed up yet with the needed reputation and credibility.
Finally some voice of reason. I felt so lonely with my arguments among all "hodl, to the moon etc." mindless cheerleaders. Thanks for that. It would be nice to hear from tonych what is his plan (if any) for relinquishing control over witnesses and breaking down the current one man cartel. It's obvious that it's very early to talk about that but some plan needs to be outlined if the system is to be considered in the future something more than privately controlled currency by one man. It's so centralized at the moment that the wallet "decentralized value" slogan sounds like a joke. That's a valid concern and freezal got it right: the network had to start centralized and no one's showed up yet with the needed reputation and credibility. I'm going to use every opportunity to relinquish control over 11 out of 12 witnesses in favor of reputable individuals/organizations/companies that are willing to be part of the network. That would make the network only stronger thanks to both their involvement and the network becoming more decentralized. |
|
|
|
|
The second round is now complete, bytes and blackbytes distributed.
Here are the exact numbers:
17,610.194028342 GB distributed (1.76% of total supply, +17.6% to the previous available supply).
New available supply: 117,610.194028342 GB.
86,658.346197160 GB were on linked addresses at snapshot time and eligible for receiving blackbytes.
37,176.880613233 new GBB (gigablackbytes) in circulation, out of which:
34,360.309831321 GBB distributed,
2,816.570781912 GBB go into the development fund.
Thank you everyone who participated, special thanks to those who supported our new community members and made their experience as smooth as possible, thank you the Transition Bot.
The next round is scheduled for the full moon of March (12 March 14:54 UTC), the conditions are exactly the same as in the 2nd round.
Meanwhile, we continue developing the Byteball ecosystem to bring the power of crypto to regular users.
|
|
|
|
|
Distribution of bytes is complete, about 17,610 GB distributed, which is worth around $1m at the current price.
Distribution of blackbytes is still under way, it'll take much longer.
|
|
|
|
We'll have our 2nd distribution round under the Full Moon, on 11th of February at 0:33 UTC.
......
Bytes to blackbytes: 1 byte on linked Byteball address gives you 0.21111 blackbytes
......
Blackbytes that remain undistributed because some people didn't move their bytes to the linked address, will be transferred to a development fund which will be used to pay for future promotion and development.
......
Only 78% of bytes are on linked addresses now. Please make sure your bytes are on the linked BB addresses, otherwise you don't receive blackbytes for them! About 83% of bytes were on the linked addresses at the snapshot time 0:44 UTC (the time of bitcoin block 452487). |
|
|
|
why is the default install path for Byteball 1.3.0 x64 for win – Program Files (x86)?
i've changed it to Program Files and everything looks good.
Actually, I have no idea, InnoSetup takes care of it and both should work. |
|
|
|
Version 1.3 released https://github.com/byteball/byteball/releases. It includes TOR support in desktop wallets:  Also fixes the recently discovered bug that caused full wallets to crash with error "empty array in query params". Other new features: * Ability to re-send blackbytes in case they were not delivered * If unit is set to GB, MB, GBB, etc, amounts are now shown with decimals |
|
|
|
|
If you experienced connection problems recently, it is because the default hub exceeded 200 simultaneous connections.
The limit is increased now.
|
|
|
|
|
Show Posts
