rty
Member
 Offline
Activity: 558
Merit: 55
|
 |
July 26, 2018, 11:14:57 AM |
|
Win32, Full Node, running on an (through a symlink) SSD, got:
Uncaught exception: Error: different props of 80ftUd7v34yJstagU5EwTu6wyyDW0yRk9XX/K8ZL36Y=, mem: {"unit":"80ftUd7v34yJstagU5EwTu6wyyDW0yRk9XX/K8ZL36Y=","level":3350626,"latest_included_mc_index":3245724,"main_chain_index":3245725,"is_on_main_chain":1,"is_free":1,"is_stable":0,"witnessed_level":3350611,"headers_commission":344,"payload_commission":157,"sequence":"good","author_addresses":["CHNK74ZY66XTYLWB45UES26G3AAS522V"],"witness_list_unit":"oj8yEksX9Ubq7lLc+p6F2uyHUuynugeVq4+ikT67X6E="}, db: {"unit":"80ftUd7v34yJstagU5EwTu6wyyDW0yRk9XX/K8ZL36Y=","level":3350626,"latest_included_mc_index":3245724,"main_chain_index":3245725,"is_on_main_chain":1,"is_free":1,"is_stable":0,"witnessed_level":3350611,"headers_commission":344,"payload_commission":157,"sequence":"temp-bad","author_addresses":["CHNK74ZY66XTYLWB45UES26G3AAS522V"],"witness_list_unit":"oj8yEksX9Ubq7lLc+p6F2uyHUuynugeVq4+ikT67X6E="}
Tried restart, still got the error, dead in the water.
Any ideas?
I have a similar error, Win64, Full Node, v2.4.2 -- This is a bugfix release that fixes crashes in full wallets, |
|
|
|
|
|
|
|
|
|
|
|
There are several different types of Bitcoin clients. Hybrid server-assisted clients like Electrum get a lot of their network information from centralized servers, but they also check the server's results using blockchain header data. This is perhaps somewhat more secure than either server-assisted clients or header-only clients.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
|
|
|
|
|
CryptKeeper
Legendary
Offline
Activity: 1981
Merit: 1023
bitcoin and altcoin enthusiast
|
|
July 26, 2018, 12:12:06 PM |
|
Win32, Full Node, running on an (through a symlink) SSD, got:
Uncaught exception: Error: different props of 80ftUd7v34yJstagU5EwTu6wyyDW0yRk9XX/K8ZL36Y=, mem: {"unit":"80ftUd7v34yJstagU5EwTu6wyyDW0yRk9XX/K8ZL36Y=","level":3350626,"latest_included_mc_index":3245724,"main_chain_index":3245725,"is_on_main_chain":1,"is_free":1,"is_stable":0,"witnessed_level":3350611,"headers_commission":344,"payload_commission":157,"sequence":"good","author_addresses":["CHNK74ZY66XTYLWB45UES26G3AAS522V"],"witness_list_unit":"oj8yEksX9Ubq7lLc+p6F2uyHUuynugeVq4+ikT67X6E="}, db: {"unit":"80ftUd7v34yJstagU5EwTu6wyyDW0yRk9XX/K8ZL36Y=","level":3350626,"latest_included_mc_index":3245724,"main_chain_index":3245725,"is_on_main_chain":1,"is_free":1,"is_stable":0,"witnessed_level":3350611,"headers_commission":344,"payload_commission":157,"sequence":"temp-bad","author_addresses":["CHNK74ZY66XTYLWB45UES26G3AAS522V"],"witness_list_unit":"oj8yEksX9Ubq7lLc+p6F2uyHUuynugeVq4+ikT67X6E="}
Tried restart, still got the error, dead in the water.
Any ideas?
I have a similar error, Win64, Full Node, v2.4.2 -- This is a bugfix release that fixes crashes in full wallets, I'm not aware of a v2.4.2 release, are you sure? Latest release on github is v2.4.1: https://github.com/byteball/byteball/releases |
|
|
|
BurtW
Legendary
Offline
Activity: 2590
Merit: 1076
All paid signature campaigns should be banned.
|
|
July 26, 2018, 01:06:53 PM |
|
Yes, the bug I am reporting happens on 2.4.1. Since there is no 2.4.2 yet maybe he is trying to say that hopefully this bug we are both having will be fixed soon in 2.4.2?
His response is cryptic but what I believe is that we are both running 2.4.1 full node, he is Win64, I am Win32, we are both getting the same error.
|
Our family was terrorized by Homeland Security. Read all about it here: http://www.jmwagner.com/ and http://www.burtw.com/ Any donations to help us recover from the $300,000 in legal fees and forced donations to the Federal Asset Forfeiture slush fund are greatly appreciated! |
|
|
ThachSanhTp
Jr. Member
Offline
Activity: 364
Merit: 4
|
|
July 26, 2018, 01:14:29 PM |
|
I cannot find BYTEBALL on CoinMarketCap, instead Byteball Bytes (GBYTE) is found.
- Total Supply: 1,000,000 GBYTE
- Price $143.49 USD
I guess 1GBYTE = 1 billion BYTEBALL.
|
|
|
|
|
|
|
aigeezer
Legendary
Offline
Activity: 1449
Merit: 1013
Cryptanalyst castrated by his government, 1952
|
|
July 26, 2018, 02:44:03 PM |
|
Yes, the bug I am reporting happens on 2.4.1.
I have what seems to be a sync issue on 2.4.1 full node fwiw, also using Win64. My symptom is that syncing appears to freeze on July 13. After some hours stuck on the same clock time, I'll stop and restart it to find that the sync clock has advanced by a couple of hours at restart but goes no farther until another restart - rinse, repeat. |
|
|
|
|
BurtW
Legendary
Offline
Activity: 2590
Merit: 1076
All paid signature campaigns should be banned.
|
|
July 26, 2018, 03:52:02 PM |
|
Yes, the bug I am reporting happens on 2.4.1.
I have what seems to be a sync issue on 2.4.1 full node fwiw, also using Win64. My symptom is that syncing appears to freeze on July 13. After some hours stuck on the same clock time, I'll stop and restart it to find that the sync clock has advanced by a couple of hours at restart but goes no farther until another restart - rinse, repeat. Are you using a HDD or a SSD for your data files? If HDD then it may be too slow. I found that until recently my HDD worked fine but with some of the most recent changes it was no longer fast enough to keep up so I switched over to my SSD and it started making good progress on catching up until this exception happened. Waiting on 2.4.2 so I can get going again... |
Our family was terrorized by Homeland Security. Read all about it here: http://www.jmwagner.com/ and http://www.burtw.com/ Any donations to help us recover from the $300,000 in legal fees and forced donations to the Federal Asset Forfeiture slush fund are greatly appreciated! |
|
|
|
serhanni
|
|
July 26, 2018, 03:58:28 PM |
|
If you haven't claimed yet don't miss your chance to get free bytes by connecting your steem account with byteball wallet. Rewards scheme: Steem reputation above 30: you get a $10 reward Steem reputation above 40: you get a $20 reward Steem reputation above 50: you get a $40 reward Steem reputation above 60: you get a $80 reward Steem reputation above 70: you get a $160 reward Check their medium account for more info. |
|
|
|
|
aigeezer
Legendary
Offline
Activity: 1449
Merit: 1013
Cryptanalyst castrated by his government, 1952
|
|
July 26, 2018, 04:00:47 PM |
|
Yes, the bug I am reporting happens on 2.4.1.
I have what seems to be a sync issue on 2.4.1 full node fwiw, also using Win64. My symptom is that syncing appears to freeze on July 13. After some hours stuck on the same clock time, I'll stop and restart it to find that the sync clock has advanced by a couple of hours at restart but goes no farther until another restart - rinse, repeat. Are you using a HDD or a SSD for your data files? If HDD then it may be too slow. I found that until recently my HDD worked fine but with some of the most recent changes it was no longer fast enough to keep up so I switched over to my SSD and it started making good progress on catching up until this exception happened. Waiting on 2.4.2 so I can get going again... Interesting. I think it was on a SSD but it might have been on a hybrid SSHD. Regardless, the problem just suddenly fixed itself. After MANY hours stuck on July 13, it is syncing again now at July 16. Red herring for your bug, I fear. Good luck with your issue. |
|
|
|
|
|
BitcoinArsenal
|
|
July 26, 2018, 05:48:43 PM |
|
I cannot find BYTEBALL on CoinMarketCap, instead Byteball Bytes (GBYTE) is found.
- Total Supply: 1,000,000 GBYTE
- Price $143.49 USD
I guess 1GBYTE = 1 billion BYTEBALL.
Yes, but Byteball is not the currency, it is called just byte. The smallest unit is one byte. One billion bytes are one gigabyte (or GBYTE). So the price on Coinmarketcap is for one billion bytes. Or better exemplified: 1 GByte = 1.000 MegaBytes = 1.000.000 KiloBytes = 1.000.000.000 Bytes |
|
|
|
|
hzjixiang
Member
Offline
Activity: 112
Merit: 10
|
|
July 26, 2018, 08:52:48 PM |
|
I still have any doubt, I preserved my seed for the pocket where I've byteballs locked in smart agreement for one 12 months. If something happens with my telephone, Will I have the ability to recover that byteball locked with this seed? or any other option to recuperate if something will go wrong
|
|
|
|
CryptKeeper
Legendary
Offline
Activity: 1981
Merit: 1023
bitcoin and altcoin enthusiast
|
|
July 27, 2018, 05:54:45 AM |
|
I still have any doubt, I preserved my seed for the pocket where I've byteballs locked in smart agreement for one 12 months. If something happens with my telephone, Will I have the ability to recover that byteball locked with this seed? or any other option to recuperate if something will go wrong
You will need a full backup to restore your smart wallets, the seed words are not enough. |
|
|
|
rty
Member
Offline
Activity: 558
Merit: 55
|
|
July 27, 2018, 11:35:13 AM |
|
Yes, the bug I am reporting happens on 2.4.1. Since there is no 2.4.2 yet maybe he is trying to say that hopefully this bug we are both having will be fixed soon in 2.4.2?
His response is cryptic but what I believe is that we are both running 2.4.1 full node, he is Win64, I am Win32, we are both getting the same error.
release byteball v2.4.2: Fixed multiple bugs that crashed full wallets Added handling of protocol (byteball:) links to pay to Steem username, such as byteball:steem/username Added full backup and restore for iOS. Restore requires iOS 11+ https://github.com/byteball/byteball/releases/tag/v2.4.2
|
|
|
|
|
|
tonych
|
|
July 27, 2018, 11:42:54 AM |
|
Version 2.4.2 released https://github.com/byteball/byteball/releases: * Fixed multiple bugs that crashed full wallets * Added handling of protocol (byteball:) links to pay to Steem username, such as byteball:steem/username * Added push notifications in iOS. Hub operators need to follow instructions at https://github.com/byteball/byteball-hub#ios to set them up * Added full backup and restore for iOS. Restore requires iOS 11+. iOS users will have to wait till the update is approved by Apple |
Simplicity is beauty
|
|
|
meterse
Copper Member
Jr. Member
Offline
Activity: 226
Merit: 8
|
|
July 27, 2018, 01:24:29 PM
Last edit: July 27, 2018, 01:38:22 PM by meterse |
|
All tsunamis start with a ripple. Since July 12 more than 48,000 Steem users have chosen to ride the Byteball wave! You can see the live data here https://byteball.co/attestors |
|
|
|
|
|
|
|
Yefet
|
|
July 28, 2018, 02:31:17 AM |
|
All tsunamis start with a ripple. Since July 12 more than 48,000 Steem users have chosen to ride the Byteball wave! You can see the live data here https://byteball.co/attestorsMy mobile byteball wallet (android, 2.4.2 light) still doesn't show the steem att bot, looks like the bot store stopped updating, what could be wrong with it  |
|
|
|
|
hp162133
Newbie
Offline
Activity: 90
Merit: 0
|
|
July 28, 2018, 03:09:45 AM |
|
The partnership with Apple and app in itunes are very great news for Byteball community, @tonych. Thanks both you and Byteball team for the amazing works. |
|
|
|
|
|
jhenfelipe
|
|
July 28, 2018, 06:02:02 AM |
|
All tsunamis start with a ripple. Since July 12 more than 48,000 Steem users have chosen to ride the Byteball wave! You can see the live data here https://byteball.co/attestorsMy mobile byteball wallet (android, 2.4.2 light) still doesn't show the steem att bot, looks like the bot store stopped updating, what could be wrong with it I have updated my Byteball Android app to v2.4.2 just now and checked the Bot store. Steem Attestation bot is present there after Accredited Investor attestation bot. Are you sure it's not in your app? That's weird if ever since we have the same version. |
|
|
|
|
|
pwpwpw
|
|
July 28, 2018, 07:15:02 AM |
|
Win32, Full Node, running on an (through a symlink) SSD, got:
Uncaught exception: Error: different props of 80ftUd7v34yJstagU5EwTu6wyyDW0yRk9XX/K8ZL36Y=, mem: {"unit":"80ftUd7v34yJstagU5EwTu6wyyDW0yRk9XX/K8ZL36Y=","level":3350626,"latest_included_mc_index":3245724,"main_chain_index":3245725,"is_on_main_chain":1,"is_free":1,"is_stable":0,"witnessed_level":3350611,"headers_commission":344,"payload_commission":157,"sequence":"good","author_addresses":["CHNK74ZY66XTYLWB45UES26G3AAS522V"],"witness_list_unit":"oj8yEksX9Ubq7lLc+p6F2uyHUuynugeVq4+ikT67X6E="}, db: {"unit":"80ftUd7v34yJstagU5EwTu6wyyDW0yRk9XX/K8ZL36Y=","level":3350626,"latest_included_mc_index":3245724,"main_chain_index":3245725,"is_on_main_chain":1,"is_free":1,"is_stable":0,"witnessed_level":3350611,"headers_commission":344,"payload_commission":157,"sequence":"temp-bad","author_addresses":["CHNK74ZY66XTYLWB45UES26G3AAS522V"],"witness_list_unit":"oj8yEksX9Ubq7lLc+p6F2uyHUuynugeVq4+ikT67X6E="}
Tried restart, still got the error, dead in the water.
Any ideas?
The latest wallet, 2.4.2 fixes this. |
|
|
|
|
