Topic: Obyte: Totally new consensus algorithm + private untraceable payments - page 575. (Read 1234315 times)

I like this, makes me feel more inclined to hold longer.  I've been very nervous about the prospects for one large dump after the final Airdrop.

What's worst? Dev trying to weight what's good for coin not for individual.

U upset because u will get 10% of free money for longer than 20% free money for shorter period?

No one said this will be done for sure. It was light convo without any proper statement.

Beside, longer distribution means better awareness and higher price per piece. Which means GB really have chance to become something huge.

Just to make things clear, this is not a change, this ultimate ratio has always been referred to in the first post since the second round.


If any slow down is planned it won't be in the next round (August's) as the ratios stay the same as the previous round. Any potential slow down will not affect the bytes to bytes ratio anyway.

It's a best practice to always refer to the first post or to Tony's latest posts for accurate information .

Creating your own public asset on Byteball has become increasingly difficult and costing a complete MByte! (see https://byteball.market).

I want to give you a preliminary introduction of the EHT 7.0
Early Having Tribe of Byteball.

I created some units  
 


They are already listed on the marketplace but not for sale.
https://byteball.market/#!/assets/oH0KLsVylJmqockFTyjbLaF4Yc3uTMAlpUOQ2AJV+Fs=

As for preliminary info, I refer you to:

https://ehtzeveno.wixsite.com/eht70

My intention is to raise awareness for Byteball and produce some smiles.
I will be on holiday for the next 2 weeks since I suddenly am too rich for work
                                                                        /unfortunately not true=1/

I am considering to turn this into a monthly reward for dodge-coiners. I think they will like the humor and free coins

Comments? Thoughts? Feel free to PM me.

plenty of time for price discovery after the distribution ...
dumpers will be regretters so it helps anyone who wants to be whale later  can buy in cheap now  

Thanks!

Of course I have the backups (full backup) but just wanted to be sure what is the easiest way...

thank you. i will stick to the official information. not random rumors. go team byteball!

Where on Earth do you see 10%?

Read the OP....

1 byte gives you .2 new bytes = 20%
or (same)
1GB gives you .2 new GB = 20%

I think you mean your Program (application) is asking to install a new version.

Yes, it is safe since it doesn't touch the wallet which is in another directory; however, it's always recommended that you make a backups.

the good times can't last forever. it's supposed to be a properly distributed coin so it makes sense to slow down and widen the distribution.

so the change of airdrop is worse than last time for GB holders too?
 only 10%? instead of 20%

please official confirmation!!!!

This change here above in red i was referring to.

Hope people will see this as move towards wider visibility for gbyte.

I've been wondering about some blackbytes-details for a while, and started testing. I've created Byteball: Blackbytes FAQ to share my test-results. If I post it in this thread it quickly disappears somewhere on page 558.

Summary:
Q. What happens when I restore an old backup after receiving blackbytes?
A. The blackbytes are gone!
Q. After restoring my backup (see previous Q.), I request the sender to click "re-send private payloads". Do I receive my blackbytes again?
A. Yes.

Q. What happens if I restore an old backup after sending blackbytes?
A. The wallet shows the wrong number of blackbytes.
Q. After restoring my backup (see previous Q.), I try to send blackbytes. Does this work?
A. No. Failure: "Could not send payment: precommit callback failed".

This is crucial to understand: after restoring an old backup, the receiving party can restore his blackbytes if the sending party re-sends them. If the sending party restores an old backup, he loses the blackbytes he had in a change address.

Q. Would a 1 out of 2 multisig wallet solve this?
A. Yes!
Suppose your computer crashes right after sending or receiving blackbytes. That means your latest backup doesn't have them. But, if you have a 1 out of 2 multisig wallet on another device, that wallet still holds your new blackbytes! After restoring the backup you have 2 different amounts of blackbytes (one correct, the other incorrect). After I've sent all blackbytes from the correct wallet to another wallet, the incorrect (multisig) wallet also shows 0 blackbytes. Problem solved, blackbytes saved!

Q. What happens to a 1-in-2 multisig wallet when blackbytes are sent when one of the two is offline?
A. Payment arrives in the online wallet. When the other wallet comes online too, it quickly updates it's blackbytes balance to the right value.

Q. Why can't I send a certain amount of blackbytes?
A. User "glitch" (on Slack) explained Blackbytes very well: "it (Blackbytes) exists in pieces of 1 2 5 10 20 50 100 etc. i figure it is like when you get your money at the start of a game of monopoly..."
From the 16MBB I sent to my test-wallet, I couldn't make any transaction for less than 100kBB. I know it is possible to make smaller payments, but only if you have the "smaller units" in your wallet.

Looks as a corrupt DB or a race condition...

My wallet asks me to install new wallet. Is it safe just to download the setup file and run the wizard or how should I proceed? Should I e.g. take some backups?

Is anyone else getting an Uncaught Exception... looks like an SQLite Error of some description... but no idea what is causing it?

My wallet has been syncing for more than 96 hours now.
Just hope after it is done there isn't anymore elongated syncs needed which surpass more than 15 minutes at a time.

One can only hope.

Since this is the main reason why I choose option #2 in doing the full install of the wallet and not just the light wallet

July and also August:
16 BTC gives 1 GBYTE airdrop
5 GBYTE gives 1 GBYTE airdrop
That's 16:5

From September, it can change. Tony's ultimate ratio would be 16:1, for example:
160 BTC gives 1 GBYTE airdrop
10 GBYTE gives 1 GBYTE airdrop

This makes holding Byteball relatively more rewarding, and allows for a "soft landing" when the airdrops end.

I have a few minor bugs. I already posted one on Slack, but it could easily be overlooked. I'll post here for reference, and send you a PM too.

1. Error missing directory

On Linux, when I start Byteball on a new clean user account without ever logging in to the desktop environment, I get this error after setting my device name:


This error doesn't happen if I create directory ~/.local/share first.
It also doesn't happen if I start the graphical desktop environment first (this creates the directory too).

To reproduce:
create new user "test4" # never log in as test4
xhost si:localuser:test4 # allow user test4 to open programs onto my current desktop
su - test4
/path/Byteball

Required fix:
Instead of giving this error, Byteball should create the directory it needs.

2. Blackbytes
It's not always possible to send any number of blackbytes.
Example: I want to send 50 kBB, but I can only send 100 kBB. I don't have smaller units in my wallet.

Required fix:
If I cannot send a certain number of blackbytes, my wallet should inform me how much I can send.
Feature request:
I would like to be able to see what units of blackbytes I have in my wallet.

3. Linux file permissions
The default file permissions on the Linux wallet are too restrictive: if I save the wallet as root, a user can't use it.
Example:
This should be:
Required fix:
All 18,000+ files should have permissions that allows "other" users to read and (if appropriate) execute them.

4. Light wallets don't stop Syncing
My wallets are "Syncing" most of the time now, for more than 36 hours. Sometimes one or a few of them are done, but all light wallets continue "Syncing" again after a while. They all have different amounts of "private payments left". Restarting a wallet sometimes solves it.
Screenshot:


Required fix:
Syncing should be much faster than this.

Any particular info?