Hello Come-from-Beyonds sockpuppet.

Nice trolling.

To all reading except the troll:

Byteball is decentralized, trustless between users/nodes, and each user/node must trust his selection of witnesses.

This is no diffrent than trusting bitcoin miners will continue their operations and bitcoin node operators. The worst that could happen if witnesses misbehave is they are replaced.

Byteball is sybil resistant, you cant do any damage by spawning millions of wallets or fake users. You can spawn a witness but it will only loose bytes as nobody has it as its selecion. You cant even replace all the 12 witnesses with fake ones.

No

1. BTC -> Byte 
=> estimated ~100000 BTC linked (at 2. round) => 6250 GByte distributed

2. Byte -> Byte
=>  100000 GBytes (10% from the first round) => 10000 GBytes  distributed

3. Total
Total: 16250 GBytes distributed at 2. round => 16250/1000000 = 1,6 %

4. Total distributed 1. + 2. round
11.6 % or 100000 (1. round) + 16250 (2. round) = 116250 Gbytes

Could you be more specific please, how would you sybil attack?

Dev:

Why send is so unstable,It  have a  lot  of bugs.

Now a days they're not adding any good coin,unless you pay their fees for instant listing.A lots of new coins were added in poloniex,but not all of them are legit and good.

why is that?

Hi tonych,

Please, let us known if the following reasoning is correct.

Say there are N wallets running on the byteball network at a given time.
All of them have the same list of 12 witnesses, all them being the 12 witnesses services you currently run to bootstrap the network securely.
Now, imagine that each one of those N wallets change 1 of their witnesses to another one, but that every one change to a different one (I know that is not the way it's meant to occur in practice, but this is a theoretical reasoning).  I mean, now there are N different witnesses plus the 12 you run.
After this, is it possible for any wallet to change its list of 12 witnesses, at the same time, by any subset of 12 witnesses from the N witnesses set there are now at the network (not your 12 ones)?

thank you for the bytes and thanks for the explanation concerning the connections through TOR.

i will try to find out what exactly is send to google. or do you already know this.

I do not know, its difficult to find out since its TLS 443.

You can also block it by saying in youretc/hosts 127.1.2.3 plus.google.com google.com but that will block for all other programs too.

To reveal what it is requesting is, if on Linux, run it with strace with filter on file/read/write and network system-calls.  

good job but don't go paranoid.

just collect the all issues and make gathered report, it would be better than separate posts.