Obyte: Totally new consensus algorithm + private untraceable payments

[zanzibar]

So far there are no exact plans. Lisk and Iconomi have agreed to do nothing until the end of the Byteball distribution.
But maybe they distribute them to their holders after that? No one knows precisely now.

Lisk will sell the bytes and keep the BTC, because at that point Lisk will most likely be dead.

[dfd1]

Is DAG somehow limited in size, or someone can make billions of transactions and bloat it?

Please read the OP:

The fees paid for storing one’s transactions (or any other data) in the Byteball database are equal to the size of the data being stored.  If the size of your transaction data is 500 bytes, you pay exactly 500 bytes (the native currency of Byteball) in fees.

So what? With a fee of 50$ someone can make DAG twice as big overnight? With a fee 500$ can make it 10 gb more? There is people who can do this just for fun. Is there some prunning mechanism what will allow to cut old transactions from database?

[ArabMist]

GBYTE crashing hard. Down to 0.5. As soon as it hits 0.45, might be a good entry point for those looking to accumulate for the long game.

[keyboard warrior]

Rumor has it all the Lisk guys will get some free byteballs    dont know if its true though, will have to wait and see 

Lisk team linked their BTC wallet to Byteball wallet and are entitled to their own percentage of the coin but what I don't know is if Lisk investors are going to share in that spoil.

So far there are no exact plans. Lisk and Iconomi have agreed to do nothing until the end of the Byteball distribution.
But maybe they distribute them to their holders after that? No one knows precisely now.

I don't think Lisk agreed to do nothing until the end of the Byteball distribution. The last LiskHQ post I could find concerning Byteball is below. LiskHQ says they are currently discussing with Tony the details of a plan, but I couldn't find any promise to do nothing until the end of the distribution. The quote says expect some news in February, but there's been none in the Lisk thread.

Is there at the moment any offical statement how Lisk will proceed with the earned Byteball amount?
Are there also some numbers available how many Byteball Lisk controlls at the moment?

Many thanks in advance!

The statement so far: for on-going operations and long-term storage.
But I think Max will comment on it in the near future.

On December 31, Lisk published the Financial Report 2016.
There you can find all the details about the financial resources of Lisk, including Byteball.

Thanks Poly, as always!

We won't dump them. I think we found a very fair method for everyone, currently discussing with Tony the details. After that we need to find a legal framework with our lawyers. Expect some news in February.

[kamiyama]

Where can I learn the wallet recovery procedure?

[davidoski]

Is DAG somehow limited in size, or someone can make billions of transactions and bloat it?

Please read the OP:

The fees paid for storing one’s transactions (or any other data) in the Byteball database are equal to the size of the data being stored.  If the size of your transaction data is 500 bytes, you pay exactly 500 bytes (the native currency of Byteball) in fees.

So what? With a fee of 50$ someone can make DAG twice as big overnight? With a fee 500$ can make it 10 gb more? There is people who can do this just for fun. Is there some prunning mechanism what will allow to cut old transactions from database?

There isn't. I'm pointing this out for a long time but nobody is listening. Byteball has the same scalability problem like any other blockchain with adjustable blocksize limit. Database grows indefinitely and hardware and bandwith are the limiting factors. Moreover if somebody wants to attack byteball by sending huge data to the database it''s pretty easy and cheap at the current price. 8 years old Bitcoin blockchain nears 100 GB and you can make byteball database that big in 1 day for just $6700.

[CryptKeeper]

Where can I learn the wallet recovery procedure?

If you have a backup from version 1.4.0 of the wallet, there is nothing to learn. You restore from the backup file and your wallet content will be overwritten with the content from the backup.

[kamiyama]

Where can I learn the wallet recovery procedure?

If you have a backup from version 1.4.0 of the wallet, there is nothing to learn. You restore from the backup file and your wallet content will be overwritten with the content from the backup.

I feel like I really learned something today. You're awesome!

[escapefrom3dom]

Is DAG somehow limited in size, or someone can make billions of transactions and bloat it?

Please read the OP:

The fees paid for storing one’s transactions (or any other data) in the Byteball database are equal to the size of the data being stored.  If the size of your transaction data is 500 bytes, you pay exactly 500 bytes (the native currency of Byteball) in fees.

So what? With a fee of 50$ someone can make DAG twice as big overnight? With a fee 500$ can make it 10 gb more? There is people who can do this just for fun. Is there some prunning mechanism what will allow to cut old transactions from database?

There isn't. I'm pointing this out for a long time but nobody is listening. Byteball has the same scalability problem like any other blockchain with adjustable blocksize limit. Database grows indefinitely and hardware and bandwith are the limiting factors. Moreover if somebody wants to attack byteball by sending huge data to the database it''s pretty easy and cheap at the current price. 8 years old Bitcoin blockchain nears 100 GB and you can make byteball database that big in 1 day for just $6700.

we definitely need an explanation from dev about it.

[SatoNatomato]

Is DAG somehow limited in size, or someone can make billions of transactions and bloat it?

Please read the OP:

The fees paid for storing one’s transactions (or any other data) in the Byteball database are equal to the size of the data being stored.  If the size of your transaction data is 500 bytes, you pay exactly 500 bytes (the native currency of Byteball) in fees.

So what? With a fee of 50$ someone can make DAG twice as big overnight? With a fee 500$ can make it 10 gb more? There is people who can do this just for fun. Is there some prunning mechanism what will allow to cut old transactions from database?

There isn't. I'm pointing this out for a long time but nobody is listening. Byteball has the same scalability problem like any other blockchain with adjustable blocksize limit. Database grows indefinitely and hardware and bandwith are the limiting factors. Moreover if somebody wants to attack byteball by sending huge data to the database it''s pretty easy and cheap at the current price. 8 years old Bitcoin blockchain nears 100 GB and you can make byteball database that big in 1 day for just $6700.

we definitely need an explanation from dev about it.

I dont think the problem exists today, of too fast growth too big load on nodes, hence low priority task. 100GB for bitcoin database is small anyway, compare with how much storage a random bank requires to run its business? Byteball database does grow fast, it can compress well, there can be other implementations to make it even smaller.

It is true the price to add shit to the database to make it grow even more is small compared to how much load/wasted-space it will cause on hubs and full wallets today, but the price is expected to rise and make such attacks more costly. I guess, even today the price is 6700 but still those 6700 are more worth for something else than to attack Byteball.

[Come-from-Beyond]

Byteball database does grow fast, it can compress well, there can be other implementations to make it even smaller.

Text is compressed much better than JPG photos. And you can't compress below some threshold if you use lossless compression. Maybe read basics of https://en.wikipedia.org/wiki/Information_theory before posting misleading "information"?

[alzheimer]

I was late for the 1st and 2nd airdrop, but I'll get my precious bytes this time!

[SatoNatomato]

Byteball database does grow fast, it can compress well, there can be other implementations to make it even smaller.

Text is compressed much better than JPG photos. And you can't compress below some threshold if you use lossless compression. Maybe read basics of https://en.wikipedia.org/wiki/Information_theory before posting misleading "information"?

Fuck off IOTA-developer, people can today gzip -9 compress the 1.2GB database to 358MB.

Not to mention, a hub or witness today is hardly putting on any CPU load, so it is even possible to keep the database in memory, compress-decompress on-demand, yet retain same throughput.

Just fuck off IOTA-scammer.

[Come-from-Beyond]

Fuck off IOTA-developer, people can today gzip -9 compress the 1.2GB database to 358MB.

Not to mention, a hub or witness today is hardly putting on any CPU load, so it is even possible to keep the database in memory, compress-decompress on-demand, yet retain same throughput.

Just fuck off IOTA-scammer.

I bet you can find JPG photos on your computer right now. Do gzip -9 on them. And imagine someone stores them in Byteball.

[Come-from-Beyond]

Fuck off IOTA-developer, people can today gzip -9 compress the 1.2GB database to 358MB.

Not to mention, a hub or witness today is hardly putting on any CPU load, so it is even possible to keep the database in memory, compress-decompress on-demand, yet retain same throughput.

Just fuck off IOTA-scammer.

I bet you can find JPG photos on your computer right now. Do gzip -9 on them. And imagine someone stores them in Byteball.

Long pause, probably still zipping. Ok, I'll explain this trivial thing, so you won't waste CPU power on zipping...

It's quite obvious that once people start to care about their GBs they'll do everything to spend as less them on fees as possible. It's a no-brainer to compress data before pushing them to Byteball storage. As the result most of data in Byteball DB will already have near-max entropy. At this point lossless compressing won't give noticeable benefit.

I hope you get now why that your post was misleading...

[ittou]

Hi,
I left the folder of BYTEBALL and installed the OS cleanly. And when BYTEBALL was started, the balance became 0.
How can I upgrade BYTEBALL? With this way, the balance will be 0 every time, so I am afraid to use it.

[SatoNatomato]

...shit from afraid IOTA developer in the Byteball thread...who seems to know more about Byteball than about IOTA...

Pay up and perform your attack on Byteball or shut up. Put your money where your mouth is.

[Come-from-Beyond]

Pay up and perform your attack on Byteball or shut up. Put your money where your mouth is.

It's not an attack. Re-read last 10 posts.

PS: It's just yet another fuckup from you, this is why you are so angry. And everyone sees it, hehe...

[kaicrypzen]

Hi,
I left the folder of BYTEBALL and installed the OS cleanly. And when BYTEBALL was started, the balance became 0.
How can I upgrade BYTEBALL? With this way, the balance will be 0 every time, so I am afraid to use it.

Can you please be a bit more specific about what you exactly did? My understanding is that you saved your data directory and reinstalled your system, however I don't understand if you restored your data directory from your backup or not ...

[SatoNatomato]

Pay up and perform your attack on Byteball or shut up. Put your money where your mouth is.

diarrea from iota mouth

Got no spare money IOTA devlopr to show how Byteball does not scale? Not even a tiny $1000? You mean you cant actually increase the Byteball database size to unscaleable levels with the money you made from hustling shittokens? How poor. Weak.