What have I lost?
Had >150k KMD yesterday, still have >150k KMD today.
That was just a signature spammer, don't expect meaningful replies from her. |
|
|
|
|
Need Disney Parental Control for posting on BTT too...
|
|
|
|
refund me my 0.2 BTC
ROFLMAO!  The high rollers arent happy lol. Shit happens, Its not the first and it wont be the last coin to have a hicup (inc. BTC) The important fact is it was identified early,will be fixed and the dev team were open and honest about what happened. Next time use Disney Parental Control feature to filter out schoolgirls with 0.2 BTC... EDIT: Interesting, how did she get those 0.2 BTC? By selling lemonade? |
|
|
|
From what I can tell the creator holds like 45% of the coin!(?)
How is that possible? Is it true? I don't think anyone would be interested in a coin in which the creator held half. How could it be used as a legitimate currency? We use dollars 90% of which are owned by a small group of people... |
|
|
|
Could be a good time to buy!?
Go ahead. |
|
|
|
Because, bitcoin is not very usable for other purposes than financial transactions, too low tps, too small other-data possible in the op_return field or whatever its called which allows only 80bytes.
80 bytes is enough to store the hash of data (to prove its integrity) and the link to the actual data which will likely be provided by a CDN. |
|
|
|
BTT was good for bootstrapping but now it only slows IOTA down. I can't longer dedicate my time to reading majority of posts in this thread for moderating. If anyone has questions to me, please, use PMs or go to http://slack.iota.org. If moderation is required - there are still few alive board moderators. |
|
|
|
It only ever seems to go up. Gets pumped a lot on Poloniex. Your thoughts?
You were shilling NEM and now you are not happy? Time to start taking the pills again. |
|
|
|
If there is a quantum computer and algorithm which can break hashes then Iota is also affected, it is just using a homemade sponge function instead of secp256k1 elliptic curve used in Byteball and bitcoin. Ofcourse the iota dev will lie and otherwise insinuate iota is somehow better at resisting quantum attacks just because he made it.  All sponge functions are resistant to quantum computers if they satisfy to requirements in http://sponge.noekeon.org/CSF-0.1.pdf. |
|
|
|
Хорошо, а есть proof of concept для такой атаки?
Вряд ли, ведь это "common knowledge", кто будет делать PoC для тривиальных вещей? |
|
|
|
Перевожу для тебя: биткойн не уязвим для атак с использованием квантового компьютера в связи с отсутствием эффективных алгоритмов взлома хешей.
Это не верно для случаев, когда владелец уже отправил транзакцию в сеть для подтверждения. В таком случае публичный ключ уже не защищен хэш-функцией. До тех пор, пока владелец не пытается потратить биткоины - это безопасно. Проблема в том, что между отправкой транзакции и её включением в блок пройдет в среднем 5 минут. Квантовый хакер может получить приватный ключ так же быстро как владелец приватного ключа - подписать транзакцию. |
|
|
|
Если транзакция зафинализируется до того, как она попадет в лапы к квантовому хакеру - нет. Иначе, да, потому что квантовый хакер переподпишет транзакцию и будет иметь ненулевой шанс, что именно его версия будет принята "свидетелями". Я предполагаю, что "свидетели" используют квантовозащищенные алгоритмы для своих подписей, иначе квантовый хакер сможет сам выступать "свидетелем". |
|
|
|
Just a notice
If you dont stop trolling me in this thread, lying, insinuating weakness in Byteball, insulting me etc, I will begin anti-Iota measures.
That is simple, for every post you make in this thread about me or irrelevant FUD, I will make 1 or 2 medium articles, and post in other more public spaces where Iota is present, and raise its issues. Youre not welcome here, I dont really give a shit about Iota, but if you are not leaving me alone here, I will piss on your rug.
LOL  |
|
|
|
This is Byteball not Storj, its main point is transactions, the database for its intended purpose will contain transactions, as it does today, which as shown compress well. If you think people will use it to store random data as a storage mechanism, as said previously, please do, go ahead, the whitepaper adresses the issue and so did main Byteball dev here, yet you can continue to spew more shit as you always do.
Very weak game CfB, and only shows my recommeded selection of distributed ledger for IoT, Byteball, to managers was right.
PS. IOTA, IoT and PoW does not compute what a joke lol.
I see you are in full denial of the reality now, I'll wait for you to cool down. The others can see how it really was... |
|
|
|
I am a programmer at big enterprise within IoT.
Of course, we have to take these words at their face value... |
|
|
|
You are talking about an attack scenario in the future while I was talking about the database growth as it was from beginning until today.
Let's recall how it was: How much hdd space do I need to download full DAG today? 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'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...
And now explain what was the purpose of your post other than to mislead people? |
|
|
|
What is your problem, creator of iota?
A dude who behaves like a con artist posts lies in this thread and noone tries to fix this, some other dudes even try to defend him. I think this is my problem. |
|
|
|
I see your post history, whats wrong with people compressing data and storing it in byteball?
Nothing wrong, it makes perfect sense. |
|
|
|
Yes, I lie to lure newbies into Byteball. /s You do, last time it was a lie that data in the DB can be compressed well. I claim that once people start using Byteball seriously they'll be storing high-entropy data and further compression won't help. |
|
|
|
What do you mean by "lying cheerleader" ?
SatoNatomato spreads lies about Byteball to lure newbies into it. |
|
|
|
|
Show Posts
