This is not the general Byteball thread, go there https://bitcointalk.org/index.php?topic=1608859

Distributions happen every full moon. Check byteball.org

Sorry, but you didnt clear anything up. checkpoints belong in forks of bitcoin, not in a DAG.

But thanks for the discussion.

Well, I wrote above explaining why that statement doesnt float, but just because you repeat your original statement, doesnt mean it is true.

Nobody looses legit one DAG forever even in such a scenario.

As described earlier, such an attack can be mounted on bitcoin users too, just change the checkpoints in the modified client too to match what the hacker-generated database has.

In both cases, to protect yourself, since this is an attack on the user and not on the network/technology, ensure you are on the right network, and the way to do that is to check with various trusted sources, use several smartphones with different ISPs, check your balance on explorers etc.

But, Byteball has something more clever than the above. Multi-signatures, just pair your wallet with another device and setup "requires 2 of 2 signatures" to transact or setup 2 of 3 devices. Simple.

Lol.

Looks like Byteball attracted its own trolls. Probably Come-from-Beyonds sockpuppets.

Well its quiet easy to rewrite the code for something not web related, we have a prototype running on an microcontroller, written in C, it speaks WebSocket. Dont let the name confuse.

UDP alone doesnt have transport layer security, most DTLS libraries Ive seen are not very tested. In any case, the transport protocol is not very important and can be changed later.

Sounds like you misunderstand how the network works right now, with the "old clients stuck, crash".

The current Byteball network, full wallets, hubs, relays, witnesses, will not magically disappear because someone hacks and modifies a link on byteball.org or github.com, even if the byteball.org hub is taken down, other hubs already can pick up the slack, they and all full wallets have the copy of the current DAG, the one seen on explorer.byteball.org.

If your malicious client downloads a modified DAG from hackers-server, where the DAG says hacker-has so much bytes, any transactions coming from it to the real network will just be trashed as spam, signatures would be invalid, by the rest of the full nodes and witnesses.

I think its scales more than dynamic blocksize blockchains, since essentially each node or group of nodes can grow its own branch at a speed limited by their hardware and the implementation they use.

Interesting discussion, and your post is not FUD at least to my eyes.

JavaScript is not the best language for safety critical systems, Rust is better, but not many people know it well yet or the cross-section of cryptocummuntiy and Rust is small, and even in Rust you could make mistakes.

For safe-code you need formal verification with languages such as coq, but then if your language is formally verified and your software is formally verified and found safe with no flaws, you still would rely on OS and other software which has faults. Then you would need to build your entire stack on something like L4 and probably make your own hardware. That task is probably out of scope for this project right now.

The scale of safety, less to more, is wide. JavaScript for other reasons, platform diversity, speed, is a good choice, as well as also not being a worse choice which is C++.

Other implementations would be welcome, tonych what would you say about other implementations in other languages? Lets say Ada which is very nice and used in safety critical systems?

WebSocket with TLS - great choice as filtering Byteball is now harder as ISPs allow WebSocket for most web-sites to function. Security wise relying on TLS / Certificate Authorities is a "defense in depth" the security of the network does not rely on it, only makes it harder to attempt bad attacks, as all content and messages are also encrypted and signed within the transport layer. Also great design!

Tonych can not generate new coins at any time - this part smells a bit like fud.

Witnesses can change, the default wallet is pulling a list from the byteball.org hub so if tonych decides a new witness is to be rolled out he can do it, the users still have the choice to tick the "Do not pull witness list from hub" option and set their own. Take note, everyone doesnt have to have 12 same witnesses, everyone is allowed 1 change, and over time all witnesses can be replaced. Of course, if it was easy to replace all witnesses at once, or if witnesses were easy to replace say by 3 allowed choices - thats a recipe for easier attacking and stalling the network. These numbers, 12 and 1 mutation are the few constants in Byteball.

If network is replaced by a malicious one, is same general problem as for bitcoin and any other network, the user if paranoid or has reasons to suspect such an attack, should check with other sources, say different smartphones on different ISPs different public DAG explorers and compare...

 

1) 1 ICO already sold their bytes, at the first distribution, the other 2 are basically unknown, they may say some things, 1 of them said they would distribute their bytes among their customers, but what they will actually do is left to see.

2) The chats are encrypted and transported on the Byteball network, relayed by relays, and stored temporarily by hubs, then delivered to wallet. Unkown to me if the messages are in the public DAG, but I doubt it, havent seen any there.

3) The app is made with Node.JS and Cordova which gives it ability to be on iOS too, but Apple may have other opinion.

You dont have technical questions, you have opinions on Byteball features being overkill.

You dont have valid technical concerns, you have concerns that Byteball is actually better than your own shit Iota coin and want to find flaws. But you fail, instead you only learn everything about Byteball is simpler and better so then you attempt to ragequit.

Byteball is alrady in the real world unlike Iota.

Also nice that  you arent here just to refute my lies as you claimed but its obvious now you change to try to hide your FUD under "concerns".

You should be concerned about your own coin and stick to your own thread.

Weak man, very embarassing, overall very weak troll.

Indeed, facts are Byteball is on several exchanges and is in live mode while Iota is still in closed beta-like quality with bigger promises and vapor than all features it has.

IOTA-dev is fearful of Byteball and is in here trolling, lying and FUDding, while Byteball devs are delivering features such as BTC-Oracle.

I am a Byteball user here, already helped solve a small security issue, cheerleading as CfB says, while all IOTA communication channels are censored and dissenting/questioning opinions muted. Here we have open un-moderated thread. Mentions of Byteball in Iota-slack is imminent ban.

Iota only has clueless altcoin "investors" and non-programmer users who dont even understand that IoT and PoW is like oil and water. Especially as they say Iotas PoW is not to mine coins but to protect each node. OMG. Laughable.

Its not a deadlock, you were proven wrong several times, your intent here is to FUD and insinuate weaknesses in Byteball, which you arent even good at.

Nobody wants you to continue posting your lies and worthless opinions here.

If you stop posting FUD, lies and deceit about Byteball I wont reply, I promise. 

That I do not give a shit about you, not even enough to accept your money. 

This is legit, the main Iota developer is in here FUDding and trolling.

Can you imagine, the Enterprise Corporation Financial Tech Cloud M2M IoT backed and Ubuntu partnership and many more Sponsored IOTA project, CfB one of the main developers wastes his time complaining about Byteball here.

That is how authentic this is. It is a very strong contender to take the cryptocurrency space in IoT.

The main developer is not anonymous, a nice community is brewing in this thread on slack. Join us!

Wow, so much sell, how will the market ever absorb this hit of an entire 8GB.

What a puny attempt at price-dumping and more spreading of fear in this thread, when your lie is called out and highlighted in a screenshot of the whitepaper.  

Got no more FUD to spread around here?

Anyone else, take the "discounted" GB and GBB, or CfB donate them to the community fund. I got my own money and dont need yours.

I dont want your scam money

Haha.

Just a moment Ill check to code to see what would happen and get back...

Here https://github.com/byteball/byteballcore/blob/master/constants.js are the 10 constants defined for Byteball network/platform/what-have-you.

If someone modified the default client or released "Byteball UnLimited Edition IoT" which modified any of those constants, the current Byteball-network would just drop them as invalid transactions, see where the errors would be thrown and transaction/unit trashed, https://github.com/byteball/byteballcore/search?utf8=%E2%9C%93&q=COUNT_WITNESSES&type=Code

If someone wanted to, you are free too, create your own new network with say for example 4 witnesses. You could do it, and offer the new networks currency to Ethereum hodlers by using the transition bot with slight modifications.

Each user is allowed to make 1 change of the 12 witnesses.  

The topic has been discussed in this thread and the Whitepaper is a very good source. You should read it. And cry, that your own design is so complicated and shitty compared to this.

Main developer cant force users to anything, aside from auto-updating all Android apps through Google Play store (but not those in coming F-Droid release, how is it coming along @portabella !?)

To be honest, I do not know what would happen if I ran a modified client today which said it has 15 witnesses, I guess it would just be dropped as invalid transaction.

If i wanted to I could start a new network, "a fork" with 15 witnesses, but its then only using the same software but not at all same.

The concept of forks is discussed in the whitepaper under the title Schisms - in Byteball it is necessary for a new network, a new Byteball in the cases when witnesses collude with each other or just loose trust by the majority users - they can then start their new network, with 13 witnesses or 12, and begin linking old bytes to the new network as is being done today from BTC to Bytes.

What I like about Byteball is that the users have so much power. Just by selecting what to use, which witness we trust. Simple.

EDIT: Just to be clear, there is weakness in Byteball in my opinion, though CfB is clearly off target by half a planet. So far its only a few developers who understand it, we need better documentation so more developers can join and begin developing apps.