I still canīt find a solution for my problem. The balance remains 0. Could it be a problem with the latest version of the wallet? Isnīt there anyone who faced the same problem before? Some help will be really appreciated :/
Maybe your wallet can't access internet cause of a firewall or something else. Try to chat with a bot to check the connectivity. |
|
|
|
Uncaught exception: Error: Error: SQLITE_CONSTRAINT: FOREIGN KEY constraint failed INSERT INTO_authors (unit, address, definition_chash) VALUES(?,?,?) ....
Can't access mac wallet
Solution please someone...
Thanks
Upgrade to 1.9.3 to fix the issue. |
|
|
|
Oh, does the bot also deposit funds into same contract? I missed this part.
Yes, you will see appear a funded smart-wallet that you can spend only if the flight is delayed/canceled. Otherwise that's the bot that will take the money back. |
|
|
|
Who gives odds?
It's based on statistics about flight you want to insure. |
|
|
|
Of course, there is insolvency issue with the bot too, same as with insurance company. If many flights will be delayed, the bot will get broke, and somebody will not get paid.
No the compensation money is put in a smart-contract, you're sure to be paid. If the bot runs out of money it will simply don't propose insurance contracts anymore. |
|
|
|
As far as I know from the flight oracle. But I'm not sure what you need to do to check it in the app. Probably need to chat with the flight oracle - it's in the bot store:
From what I see in code, the insurance bot sends a message to user when the status of the flight is known. It communicates also with the bot oracle to make it inserting the flight status in DAG so you don't need to chat with the oracle. |
|
|
|
The other question that arrives is who decides which bot is added to the bot store? If I copy-paste the bot that tonych just opensourced and start running a similar bot will it be added to the bot store automatically? If not, who decides which bot is added to the bot store and which is not?
The bot store is broadcasted by the hub owner. You would have to contact the differents hubs available to ask them to add your bot. |
|
|
|
whats the chance this airdrop is a scam to collect signed info, for some sort of hack....i know ecsda still protects your BTC, but still.....
you lose the SHA256, and RIPEMD160 protections for that address, now only having ECDSA.
There must always be a risk for any action.....
sure you could move your coins just before and after the snap shot, but I would expect they are ready for that.
Also who really wants to crack open cold storage? Then have to move that all around....
Without Byteball, there are already plenty funded BTC addresses which signed at least 1 transaction. If someone would be able to crack them, he wouldn't need Byteball distribution for that. |
|
|
|
This is a good coin with many nice features, I think dev should promote it more, so more people will know it.
Do you have ideas for promotion ? Remember there was no ICO for Byteball so nobody is paid to do marketing. |
|
|
|
Why did the price fall so much? Has the ball been attacked? Or what other reason? CFB the gay is attacking every day, is he in the dish, the author think of ways, let him not toss about.
Nothing special is happening, Byteball works well. |
|
|
|
|
Light is an option to choose when you install the wallet.
|
|
|
|
If the witness is attacked by DDOS, and the 12 witnesses are attacked and unable to issue witness blocks, what shall we do? Does byteball's network stop? Will it be as unsafe as DPOS?
Witnesses are likely hidden with TOR so you won't be able to find them even with the complicity of the hub they are connected to. In the case you still managed to find their IP, you would need a huge DDOS power to take all them down since they are hosted all around the world on several networks all having their own DDOS protections. Is it safer to have 100 witness than just 12? Would more resources (block size) be required if there is more witness? The choice of 12 witnesses is explained in whitepaper: We require that the number of witnesses is exactly 12. This number 12 was selected because:
it is sufficiently large to protect against the occasional failures of a few witnesses (they might prove dishonest, or be hacked, or go offline for a long time, or lose their private keys and go offline forever)
it is sufficiently small that humans can keep track of all the witnesses to know who is who and change the list when necessary
the oneallowed mutation is sufficiently small compared with the 11 unchanged witnesses. 100 witnesses would require too much much work for an individual to investigate about each witness and determinate if he can be trusted or not. |
|
|
|
If the witness is attacked by DDOS, and the 12 witnesses are attacked and unable to issue witness blocks, what shall we do? Does byteball's network stop? Will it be as unsafe as DPOS?
Witnesses are likely hidden with TOR so you won't be able to find them even with the complicity of the hub they are connected to. In the case you still managed to find their IP, you would need a huge DDOS power to take all them down since they are hosted all around the world on several networks all having their own DDOS protections. |
|
|
|
I still hold the bag for the byteball on the trading site, I think I am still worried about losing money in the wallet, I want to keep it in my wallet but worried about losing it because of my mistake not storing backups of my wallet
Look at multi-device wallet, a nice feature implemented natively in Byteball (you don't depend of a possibly bugged smart-contract like in ETH  ) You can create 1 of 2 required signature wallet so your bytes are still spendable even if you lose one device. You can create 2 of 2 required signature wallet to increase security, an attacker would have to hack your both devices to steal your money. |
|
|
|
You have no place in the crypto world without a fast SSD, you would never sync up the bitcoin chain in your life with a HDD.
You're exagerating a bit. I synced BTC chain with an old HDD laptop in less than 1 week. I run 2 full Byteball nodes on a HDD dedicated server and it's fine. It looks like Searing got another problem. Right now it took my PC 5-6 minutes for a day of DAG, HDD is at least 10x slower than SSD (and 100x less 1kb or less I/O) so if the DAG will continue to grow in this pace, it will take an hour for every day of DAG, that's 1day sync time for 24 days of DAG using an HDD, good luck syncing up a full node next year with an HDD  If you must use HDD, make sure it is not your OS drive because that's when it gets seriously slow, HDDs cannot deal with many operations at once. Also laptops usually have only 1 drive, so if that's not an SSD then it's a nightmare to sync up any blockchain/dag. Ofc once you synced up, it can easily handle being a full node. I stay with HDD for my full nodes cause with more space available they make Byteball network more resistant to a spam attack. I agree it will be hard to sync a new Byteball full node in future but there will be solutions. There is still some room for DB optimisation and we can imagine the witnesses attesting a DB backup available for download so you wouldn't have to check all the DAG to set up a new full node. |
|
|
|
You have no place in the crypto world without a fast SSD, you would never sync up the bitcoin chain in your life with a HDD.
You're exagerating a bit. I synced BTC chain with an old HDD laptop in less than 1 week. I run 2 full Byteball nodes on a HDD dedicated server and it's fine. It looks like Searing got another problem. |
|
|
|
I think this is really cool. Is there more exciting news about Byteball?
Obviously the price has never recovered. I remember $800-$900.
Now we're at only $466
Don't forget that bytes holders get 20% more coins at each distribution, this almost compensates the price drop. In a crypto market going down in overall that's not so bad. The exciting news about Byteball is that it works without flaws as described in white paper and it's given for free. This is not the usual get-rich-quick ICO scheme, don't expect it to be pumped with bullshit news. I expect rather a slow grow sustained by people technically minded (they are a lot on Byteball Slack) until someone launches a killer smart-contract that becomes viral spreaded by P2P. In light wallet smart contract working?
Yes light wallets are enough for everyday uses. |
|
|
|
Need wait 15 days for difficulty fall:
If hashrate falls, you won't be able to mine the blocks needed to reach next difficulty adjustement (that happens every 2016 blocks). |
|
|
|
You've probably heard about the Parity multi-sig smart-contract hack ? https://blog.aeternity.com/parity-multisig-wallet-hack-47cc507d964dEven if the devs are honests, they can still do big mistake... This shows how the Byteball smart-contracting approach is pertinent, by offering simple contracts definition that people can review themself, they don't have to trust any devs. |
|
|
|
|
Show Posts
