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

I downloaded the purse but it's very long synchronized and there is a lighter version of what I heard something like that

Which are the tecnical requirements and procedures to become a registrar? Are we moving in uncharted territories or are there already precise procedures and instruments set for that?

Freebe Blackbyte Exchange Report

Lots of new traders joined the Blackbyte Market lately. New constant volume and a good price increase (0.03 -> 0.04) gives a very good feeling about the blackbyte market development!

• 24h volume: 1065 GBB
• Last trade: 9 GBB at: 0.0379

• Best Ask: 0.04 (50 GBB)
• Best Bid: 0.0402 (0.99 GBB)
• Total GBB wanted: 5993
• Total GBB for sell: 714

• Total volume all time: 64113 GBB
• Total successful trades: 1041

---

---

Wow, this have been very exhausting and I like it. 1 KB = 1000 byte is the simplest and for classic future coin users the best to understand. Everything else seems to me useless. For the IT guys maybe it would be better, but for classic user not. And I think all of us want to see Byteball with as many users as is possible and with the price on high which this coin deserves...not like now, which is ridiculous.

If it saves you time and hassle you wouldn't mind a higher fees which for little amounts would be irrilevant. Moreover, if you want to change bytes with some specific alts on an exchange you would probably have to go a double change, passing through BTC or ETH or whatever major market, which would anyway double the fees. Plus add transfer fees. So this new bot is super-welcome.

Asset names are supposed to be assigned by trusted users/businesses called registries.  Any number of registries can exist, and each hub will have a list of registries it trusts.  Only names assigned by trusted registries will be broadcast to wallets connected to the hub.

Absolutely. And the scheme that I outline takes advantage of that happy mnemonic near-coincidence. Without any drawbacks. And eliminates the ambiguity that has led to fuckup after fuckup after fuckup after...


Nobody later decided that - the prefix 'k' or 'kilo' has denoted exactly 1000 since long before the dawn of logic-based computing.


It is used by every thinking person that values precision.


Universities absolutely teach the difference between 1000 and 1024, and the difference between metric powers-of-ten units and binary prefix powers-of-two units. Sure, there may be some backwaters that are still stuck in the eighties*, clinging to a misleading and imprecise anachronism. But by and large, the difference is known and taught - everywhere that values truth.

*Actually, I graduated with an Electrical Engineering degree in the eighties. And while we didn't yet have the convenient binary prefix notation back then, we were absolutely taught that misusing metric prefixes as an approximation was exactly that - an approximation. And not strictly correct. And to always be mindful of the error and ambiguity inserted due to this misuse.


Linux certainly knows how to report memory and disk capacities in KiB, MiB, GiB, TiB, ... Of course, if your favorite clownshoe hides the truth from you, don't put that on Linux - put it on your dumbed down distro. And don't talk to me about Windows as if it is some paragon of Vires in Numeris. Last time I bothered to look, Windows couldn't even agree with itself. What with it reporting a GB as (something like) 1024*1024*1000 in Disk Mangler and as 1024*1000*1000 in File Mangler. Or some equivalent comedy of hapless errors.


Hoo-boy. we got a live one here. I suppose you think NIST is ignorant on computing? ISO? IEEE? ACM? IETF?


Cool. You've said a second thing that isn't 100% wrong. But conversely, just because you say that 1000=1024 does not mean it is.


This has exactly zero to do with the discussion at hand. However, this could be good for a couple of laughs. Please explain to me the physics behind your assertion that one cannot build a memory chip that holds exactly 1000 bytes of information. On second thought, don't. We don't need the fruitless diversion. Nor the ensuing hilarity.

So now that that is out of the way, let me try again. If we use the binary prefixes when we are speaking of 2^(10*n):
- we remove the ambiguity of not knowing if a measurement of (e.g.) 'M' means 1000000 or if it means 1,048,576 (or even 1,024,000);
- we lose none of the brevity of compact notation;
- we lose none of the mental chunking that comes from conveniently scaled units;
- we stop losing time and money due to fuckups in unit misunderstandings;
- we are using the units that all serious and conscientious scientists and engineers use;
- we stop killing people; and
- when the legacy Bitcoin max block size is 1MB, we know instantly it is 1,000,000 bytes, not 1000*1024 bytes, nor 1024*1024 bytes (guess what - 1,000,000 is exactly what it is - it is NOT 1,048,576)

Look, it's OK to be ignorant. There's no shame in that. I'm sure I am ignorant on any number of topics. However, to cling to a deprecated, failure-prone anachronism -- after being shown the error of your ways -- is downright foolish. And that is indeed shameful.

Stop misusing metric unit prefixes as approximations of binary powers-of-two. Before they kill again.

Byteball featured in BitcoinGarden’s newsletter

https://bitcoingarden.org/forum/index.php?topic=22314.0

It's not a windows/linux thing, it's more of a hard disk/memory thing: 
https://superuser.com/questions/1080633/confusion-with-storage-capacity-powers-of-10-and-2

Actually, while windows has always expressed sizes in powers of 2, I'm looking at a linux machine right now (xubuntu 16.04 specifically) which expresses them in powers of 10 and I remember it being this way for years, accross various distros

You could not be more wrong if you tried.

Kilo (K), Mega (M), Giga (G), Tera (T), etc. were powers of 10 long before they were lazily used as powers of two for devices that happen to address in binary, for example computer memory chips.

Kibi (Ki), Mebi (Mi), Gibi (Gi), Tebi (Ti) etc. are the accepted and internationally standardized prefixes for powers of 2.

Therefore 1 Kilobyte is 1000 bytes, 1 Kibibyte is 1024 bytes.  If you use 1 Kilobyte to say 1024 bytes you are wrong.

I just used the Freebe bot in the wallet to trade blackbytes.  It worked as advertised.  There is a guide at http://freebe.byte-ball.com

I imagine the other bot works well to, it's just that this one I had an easier time figuring out.  While exchanges are great, it's nice to see a peer to peer solution!

WIll blackbyte be added to an exchange in the near future? Is anything planed like that? I would like to see it

Yep. You have to peer your wallet with the other guy wallet then he asks your for a Blackbytes payment in the chat.

can you send blackbytes to someone else?

thx

No, I didn't

I'm on v1.11.5 and my wallet just caught up to the point where the last distribution occurred, but then I got the "removing stable units" error. I see 1.11.5 was supposed to fix this error. Might there be another reason why I'm seeing this message? Any suggestions on how to rectify it?

I'd hate to rain down on your parade but in case of bytes, powers of two actually make sense. It was not lazy. Whoever later "decided" that 1 KB = 1000 bytes was a moron, whenever it's published on NIST or not. It's not used by anyone. Universities don't teach it that way. Your operating system (whenever if it's windows or linux) doesn't show it that way. 1 KB = 1000 bytes is only in the head of some senile bureaucrats that don't understand technology and memory alignment. Just because a bureaucrat says the earth is flat it doesn't mean it is. You can't wish it that way, just like you can't make a memory chip that holds exactly 1000 bytes of information. Bytes are stored in binary. That's the reality.