Author

Topic: [PoS+PoW] eXocoin [EXO]-gen 2.0- dev. from scratch! Give-Away | Open Beta - page 189. (Read 415654 times)

newbie
Activity: 34
Merit: 0
please send me some test EXOs. will send them back with simple interest of 100%  Grin

EXOyahgZ5Csz31ctmnK22arfAUUWAaZRs1gxdbhd
send

paid only 10% interest due to the risk of bankruptcy  Cheesy

I invested in second stage and got permission from you before applying for e-mail giveaway. But you refused my application.
sr. member
Activity: 476
Merit: 250
So we needed 150 posts to benefit from the email giveaway?  Was that mentioned anywhere because I don't remember seeing it.  Sucks because I've lurked on here for a while now but didn't join until this year.

Here's my address if you change your mind.

EXOSftmg9m1tpKbxw94WeGTMtG2G11parKHYdamk
sr. member
Activity: 294
Merit: 250
please send me some test EXOs. will send them back with simple interest of 100%  Grin

EXOyahgZ5Csz31ctmnK22arfAUUWAaZRs1gxdbhd
send
newbie
Activity: 17
Merit: 0
hm strange.. when searching for EXORGxHC1e1h2Dq6QgNpnhy32gTbh2BC2gFycmgc in the block explorer the 666.667 does not appear. The other address to that transaction is displaying the amount.
That will be investigated - as well as the rounding of 667. But that are just minor bugs. If all nodes survive the next 12 hours then we are happy Wink

It is not a problem with using doubles at all. They have a precision of 15 decimals, we capped it at 12. So the 12th decimal will be a rounded value but not the third one like here. But let us check whats the issue here.
Doubles are an issue in comparisions if they are not properly addressed. But with capping/rounding at 12th decimal there should not be an issue anyway. I, personally, never got in trouble with this processing of data but correct me if I am wrong. We could use unsigned long long anyway for V0.6


Right now after ~7 hours running nodes (some ~10) all are still in sync and fully functional. That's the all-time best message here I guess ;-) No crashes or asyncs yet. Crossing fingers for the next hours...




#edit
I just was messing around with 666.666 EXO  Grin

However, client sent 666.667

So I created EXO out of nowhere  Shocked

What's causing this? Is this some floating point bug?
Do you use floating point at all?


I sent about 666.666666666666666666 in the form
Exo-client sent 666.667 so he round to 3 decimals.

I dont know how is that so. But actually 666.667 left the wallet. So no "problem" at all, just rounding issue
Ah ok exokk most possibly capped the counting decimals of transactions within the GUI interface to 3 decimals and rounds it properly. I'll ask him/check it and will increase it

I also had an issue with gnerating a first time address: Client crashed and abter doing the same again it worked.
I got 20000 Beta-Exo, maybe thats the issue...  Grin
newbie
Activity: 34
Merit: 0
please send me some test EXOs. will send them back with simple interest of 100%  Grin

EXOyahgZ5Csz31ctmnK22arfAUUWAaZRs1gxdbhd
sr. member
Activity: 476
Merit: 250
sr. member
Activity: 294
Merit: 250
hm strange.. when searching for EXORGxHC1e1h2Dq6QgNpnhy32gTbh2BC2gFycmgc in the block explorer the 666.667 does not appear. The other address to that transaction is displaying the amount.
That will be investigated - as well as the rounding of 667. But that are just minor bugs. If all nodes survive the next 12 hours then we are happy Wink

It is not a problem with using doubles at all. They have a precision of 15 decimals, we capped it at 12. So the 12th decimal will be a rounded value but not the third one like here. But let us check whats the issue here.
Doubles are an issue in comparisions if they are not properly addressed. But with capping/rounding at 12th decimal there should not be an issue anyway. I, personally, never got in trouble with this processing of data but correct me if I am wrong. We could use unsigned long long anyway for V0.6


Right now after ~7 hours running nodes (some ~10) all are still in sync and fully functional. That's the all-time best message here I guess ;-) No crashes or asyncs yet. Crossing fingers for the next hours...




#edit
I just was messing around with 666.666 EXO  Grin

However, client sent 666.667

So I created EXO out of nowhere  Shocked

What's causing this? Is this some floating point bug?
Do you use floating point at all?


I sent about 666.666666666666666666 in the form
Exo-client sent 666.667 so he round to 3 decimals.

I dont know how is that so. But actually 666.667 left the wallet. So no "problem" at all, just rounding issue
Ah ok exokk most possibly capped the counting decimals of transactions within the GUI interface to 3 decimals and rounds it properly. I'll ask him/check it and will increase it
ATC
newbie
Activity: 49
Merit: 0
Looking forward to test the new version!  Smiley

An advice from an old c++ coder:
Quote
bugfix: double-round function was not accurate enough for one comparision

Don't use floating point in a financial application! Nasty round and compare bugs ahead!  Shocked

Use a long or longlong and do integer division to get to the decimals.

Yes that might be a good idea;-) Right now it will round it to 12 decimals accuracy and is working as well.... but we will consider changing that.

Make that priority, please. Before the release date. Floating points should not be used in financial applications.

+1

Make it priority! Only integer in finance.

BTW, anyone with address in the recent posts will get 8888.88 exo.
newbie
Activity: 17
Merit: 0
I just was messing around with 666.666 EXO  Grin

However, client sent 666.667

So I created EXO out of nowhere  Shocked

What's causing this? Is this some floating point bug?
Do you use floating point at all?


I sent about 666.666666666666666666 in the form
Exo-client sent 666.667 so he round to 3 decimals.

I dont know how is that so. But actually 666.667 left the wallet. So no "problem" at all, just rounding issue
newbie
Activity: 34
Merit: 0
Looking forward to test the new version!  Smiley

An advice from an old c++ coder:
Quote
bugfix: double-round function was not accurate enough for one comparision

Don't use floating point in a financial application! Nasty round and compare bugs ahead!  Shocked

Use a long or longlong and do integer division to get to the decimals.

Yes that might be a good idea;-) Right now it will round it to 12 decimals accuracy and is working as well.... but we will consider changing that.

Make that priority, please. Before the release date. Floating points should not be used in financial applications.

yes. I have had nightmares working with double in financial modelling. Please change it to long before the final release
sr. member
Activity: 338
Merit: 250
I just was messing around with 666.666 EXO  Grin

However, client sent 666.667

So I created EXO out of nowhere  Shocked

What's causing this? Is this some floating point bug?
Do you use floating point at all?
hero member
Activity: 714
Merit: 500
Im liking what im reading here  Grin
sr. member
Activity: 294
Merit: 250
I just was messing around with 666.666 EXO  Grin

However, client sent 666.667

So I created EXO out of nowhere  Shocked

Yup...  got it!    Grin

The eXominer seems to be working too...  but I have a question...  why does it stop hashing away in order to submit to parent?     Undecided
that is the key innovation regarding our mining system: if you find a system you submit it and therafter up to the start of the next block your miner will idle. ->Saving you energy costs! The faster you find a result the more EXO you'll get and the less energy cost you will have (procentually regarding hashpower).
As stated, you'll get hopefully some mining transactions after block 100 has been reached
newbie
Activity: 17
Merit: 0
Does the bug reply section already work?
newbie
Activity: 24
Merit: 0
...  sent 3333 EXO right back!!!     Grin

Got it!  Cheesy

EXOk3Z2aewR5asfdpT6qCFcO5gxDtTNDyw4tdbhg

sent you some

Just got 333.33.
legendary
Activity: 1708
Merit: 1000
Reality is stranger than fiction
sr. member
Activity: 294
Merit: 250
PLease send me some for test EXO6ZqUDk8rexbs4uPztfK69WKUYPATSSrRndbgm

send: TX55935C7CA5900A81108DF73336EDA8E363A65D8AC35B46D29428F8DC17E6954C



btw: mining will hopefully start at block 100 automatically (watch block explorer mining value or mining tab)
newbie
Activity: 24
Merit: 0
I was very generous transfering 0.1 EXO Wink

WOW! Thanks a lot.  Shocked
Got it.  Cool
newbie
Activity: 17
Merit: 0
I just was messing around with 666.666 EXO  Grin

However, client sent 666.667

So I created EXO out of nowhere  Shocked
legendary
Activity: 1708
Merit: 1000
Reality is stranger than fiction
...  sent 3333 EXO right back!!!     Grin

Got it!  Cheesy

EXOk3Z2aewR5asfdpT6qCFcO5gxDtTNDyw4tdbhg

sent you some
Jump to: