Witnesses do not decide ordering of units. Ordering is determined by the algorithm that looks back at the witnesses-authored units in the DAG.
What TPS limit do you expect to see in the real world (order of magnitude)?
Topic: Obyte: Totally new consensus algorithm + private untraceable payments - page 900. (Read 1234271 times)
February 09, 2017, 06:18:28 AM
What TPS limit do you expect to see in the real world (order of magnitude)?
February 09, 2017, 06:15:29 AM
I was reading Gavin Wood's polkadot paper and came across this:
"Tangle [17] —becomes impractical."
How does byteball deal with arbitrary state changes?
Byteball has the ball its in the name, that is the global state, witnesses decide it. Witnesses decide ordering of units. This is not "the tangle" where developers decide the consensus with milestones and snapshots."Tangle [17] —becomes impractical."
How does byteball deal with arbitrary state changes?
Witnesses do not decide ordering of units. Ordering is determined by the algorithm that looks back at the witnesses-authored units in the DAG.
The important thing to note in relevance to the quote which spurred discussion, is that there is an ordering.
February 09, 2017, 06:15:09 AM
You had ample opportunity to explain all my concerns in the IOTA Unmoderated thread...
In a thread dedicated solely for trolling? C'mon. I won't waste time there.
I'm here to reveal your lies. You are still doing all those tricks that scammers do to conduct a long con.
February 09, 2017, 06:09:21 AM
I was reading Gavin Wood's polkadot paper and came across this:
"Tangle [17] —becomes impractical."
How does byteball deal with arbitrary state changes?
Byteball has the ball its in the name, that is the global state, witnesses decide it. Witnesses decide ordering of units. This is not "the tangle" where developers decide the consensus with milestones and snapshots."Tangle [17] —becomes impractical."
How does byteball deal with arbitrary state changes?
Witnesses do not decide ordering of units. Ordering is determined by the algorithm that looks back at the witnesses-authored units in the DAG.
February 09, 2017, 06:01:53 AM
This is not "the tangle" where developers decide the consensus with milestones and snapshots.
You are again spreading lies. I bet you'll play chicken if I ask you to put your money where your mouth is.
You had ample opportunity to explain all my concerns in the IOTA Unmoderated thread - which you didnt, instead you, and iotatoken guy, again attacked me verbally and domsch fake acted nicely without in any way addressing technical concerns. And no selling vaporware and imaginary future where it will magically work doesnt count as a good answer.
Ive seen what shit you write about Byteball in your slack channel - now there we can talk about FUD and lies.
February 09, 2017, 06:01:37 AM
I'll do the 2nd round distribution on testnet later today.
If you participated in the 1st round, get your testnet wallets ready and synced.
The pairing code of testnet transition bot is A89N05sSYB+ZakW6HH16mAHuFsf+HDi+Us3DeP/[email protected]/bb-test#0000
If you participated in the 1st round, get your testnet wallets ready and synced.
The pairing code of testnet transition bot is A89N05sSYB+ZakW6HH16mAHuFsf+HDi+Us3DeP/[email protected]/bb-test#0000
Testnet distribution is complete, please check your balances if you linked your testnet coins.
Dust-size balances were not credited with new bytes: if an address had balance less than 10000 bytes (i.e. less than 1000 new bytes to be received), it was ignored.
February 09, 2017, 05:12:12 AM
Dear Cryptox users. We recommend to take out of exchange your BTC and GBYTE balances in order to participate in 2nd round of Byteball distribution.
Those who forget, will be credited according to their 95% balance BTC and 95% GBYTE at the time of transition.
Blackbytes will wait for you to contact [email protected]
Those who forget, will be credited according to their 95% balance BTC and 95% GBYTE at the time of transition.
Blackbytes will wait for you to contact [email protected]
February 09, 2017, 04:49:32 AM
Is is possible to link multiple addresses?
||
V
You'll receive all bytes at the first BB address. It's perfectly legal to link several Bitcoin addresses to the same BB address.
Perhaps a small addition to the general understanding for the new:
If you browse here http://transition.byteball.org/ . Then you will see that this is very common.
It is also more convenient than any BTC address to link to a new / discrete BB address (this is also possible).
In such a case, after each distribution, the shares received at the various BB addresses must be consolidated again at the address specified by the bot (primary BB address). This is needed to receive blackbytes for all these bytes (in the following distribution(s)).
If you only use one BB address (and connect multiple BTC addresses with this), then this is not required.
If you don’t touch the wallet (trade, buy .. Bytes), you will automatically get your blackbytes for the shown bytes in every round.
The BTC's can be transferred from the linked address some hours after the snapshot.
They must then be shown again to the next round(s) (at one of the linked BTC-addresses or a newly linked BTC-address).
February 09, 2017, 04:21:20 AM
This is not "the tangle" where developers decide the consensus with milestones and snapshots.
You are again spreading lies. I bet you'll play chicken if I ask you to put your money where your mouth is.
February 09, 2017, 03:57:37 AM
I was reading Gavin Wood's polkadot paper and came across this:
"Tangle [17] —becomes impractical."
How does byteball deal with arbitrary state changes?
Byteball has the ball its in the name, that is the global state, witnesses decide it. Witnesses decide ordering of units. This is not "the tangle" where developers decide the consensus with milestones and snapshots. "Tangle [17] —becomes impractical."
How does byteball deal with arbitrary state changes?
February 09, 2017, 01:07:58 AM
I was reading Gavin Wood's polkadot paper and came across this:
"Tangle [17] is a novel approach to consensus systems.
Rather than arranging transactions into blocks and forming
consensus over a strictly linked list to give a globally
canonical ordering of state-changes, it largely abandons
the idea of a heavily structured ordering and instead
pushes for a directed acyclic graph of dependent transactions
with later items helping canonicalise earlier items
through explicit referencing. For arbitrary state-changes,
this dependency graph would quickly become intractable,
however for the much simpler UTXO model2
this becomes
quite reasonable. Because the system is only loosely coherent
and transactions are generally independent of each
other, a large amount of global parallelism becomes quite
natural. Using the UTXO model does have the effect
of limiting Tangle to a purely value-transfer “currency”
system rather than anything more general or extensible.
Furthermore without the hard global coherency, interaction
with other systems—which tend to need an absolute
degree knowledge over the system state—becomes impractical."
How does byteball deal with arbitrary state changes?
"Tangle [17] is a novel approach to consensus systems.
Rather than arranging transactions into blocks and forming
consensus over a strictly linked list to give a globally
canonical ordering of state-changes, it largely abandons
the idea of a heavily structured ordering and instead
pushes for a directed acyclic graph of dependent transactions
with later items helping canonicalise earlier items
through explicit referencing. For arbitrary state-changes,
this dependency graph would quickly become intractable,
however for the much simpler UTXO model2
this becomes
quite reasonable. Because the system is only loosely coherent
and transactions are generally independent of each
other, a large amount of global parallelism becomes quite
natural. Using the UTXO model does have the effect
of limiting Tangle to a purely value-transfer “currency”
system rather than anything more general or extensible.
Furthermore without the hard global coherency, interaction
with other systems—which tend to need an absolute
degree knowledge over the system state—becomes impractical."
How does byteball deal with arbitrary state changes?
February 09, 2017, 01:02:54 AM
Is is possible to link multiple addresses?
||
V
You'll receive all bytes at the first BB address. It's perfectly legal to link several Bitcoin addresses to the same BB address.
February 08, 2017, 09:20:44 PM
Is is possible to link multiple addresses? I have one address linked right now and it's telling me to move all my funds to that address, but I don't want to do it because I'm holding ~1 BTC on an address I intend to use for something else, and it's important that those funds stay there.
February 08, 2017, 07:14:28 PM
i have a prpblem with chatting with the transition bot.
i created already a wallet but everytime when i click on "chat with the transition bot"
i cant send a message to him. i tried to send my byteball adress to him but i always get in red delayed: ("code"."self_signed_cert_in_chain")
can someone help me?
i created already a wallet but everytime when i click on "chat with the transition bot"
i cant send a message to him. i tried to send my byteball adress to him but i always get in red delayed: ("code"."self_signed_cert_in_chain")
can someone help me?
it's nodejs issue.
OS/wallet ver.?
I have win 7 32bit
wallet version 1.2.0
wthat's the PF path name: «C:\Program Files» or «c:\Program Files»?
have u got some antivirus running (try to temporary disable it)?
i temporary disabled the antivirus and now it works i try to set byteball to the security exception.
thank you very much for your help
ur welcome. ☺
February 08, 2017, 07:11:32 PM
i have a prpblem with chatting with the transition bot.
i created already a wallet but everytime when i click on "chat with the transition bot"
i cant send a message to him. i tried to send my byteball adress to him but i always get in red delayed: ("code"."self_signed_cert_in_chain")
can someone help me?
i created already a wallet but everytime when i click on "chat with the transition bot"
i cant send a message to him. i tried to send my byteball adress to him but i always get in red delayed: ("code"."self_signed_cert_in_chain")
can someone help me?
it's nodejs issue.
OS/wallet ver.?
I have win 7 32bit
wallet version 1.2.0
wthat's the PF path name: «C:\Program Files» or «c:\Program Files»?
have u got some antivirus running (try to temporary disable it)?
i temporary disabled the antivirus and now it works i try to set byteball to the security exception.
thank you very much for your help
February 08, 2017, 07:04:04 PM
i have a prpblem with chatting with the transition bot.
i created already a wallet but everytime when i click on "chat with the transition bot"
i cant send a message to him. i tried to send my byteball adress to him but i always get in red delayed: ("code"."self_signed_cert_in_chain")
can someone help me?
i created already a wallet but everytime when i click on "chat with the transition bot"
i cant send a message to him. i tried to send my byteball adress to him but i always get in red delayed: ("code"."self_signed_cert_in_chain")
can someone help me?
it's nodejs issue.
OS/wallet ver.?
I have win 7 32bit
wallet version 1.2.0
what's the PF path name: «C:\Program Files» or «c:\Program Files»?
have u got some antivirus running (try to temporary disable it)?
February 08, 2017, 07:00:55 PM
i have a prpblem with chatting with the transition bot.
i created already a wallet but everytime when i click on "chat with the transition bot"
i cant send a message to him. i tried to send my byteball adress to him but i always get in red delayed: ("code"."self_signed_cert_in_chain")
can someone help me?
i created already a wallet but everytime when i click on "chat with the transition bot"
i cant send a message to him. i tried to send my byteball adress to him but i always get in red delayed: ("code"."self_signed_cert_in_chain")
can someone help me?
it's nodejs issue.
OS/wallet ver.?
I have win 7 32bit
wallet version 1.2.0
February 08, 2017, 06:57:38 PM
i have a prpblem with chatting with the transition bot.
i created already a wallet but everytime when i click on "chat with the transition bot"
i cant send a message to him. i tried to send my byteball adress to him but i always get in red delayed: ("code"."self_signed_cert_in_chain")
can someone help me?
i created already a wallet but everytime when i click on "chat with the transition bot"
i cant send a message to him. i tried to send my byteball adress to him but i always get in red delayed: ("code"."self_signed_cert_in_chain")
can someone help me?
it's nodejs issue.
OS/wallet ver.?
February 08, 2017, 06:56:38 PM
i have a prpblem with chatting with the transition bot.
i created already a wallet but everytime when i click on "chat with the transition bot"
i cant send a message to him. i tried to send my byteball adress to him but i always get in red delayed: ("code"."self_signed_cert_in_chain")
can someone help me?
i created already a wallet but everytime when i click on "chat with the transition bot"
i cant send a message to him. i tried to send my byteball adress to him but i always get in red delayed: ("code"."self_signed_cert_in_chain")
can someone help me?
February 08, 2017, 04:55:21 PM
Sorry for maybe a dumb question:
I wanted to link the BB address to get BlackBytes for the next giveaway. The bot says:
However, the ammount of GB it shows, is less than I have in my wallet in the actual address.
Am I missing anything? Are there some kind of "change addresses" where BB goes to when I make transactions? I would appreciate your help. TY!
I wanted to link the BB address to get BlackBytes for the next giveaway. The bot says:
Quote
You also receive 0.21111 blackbytes for each 1 byte of your balance on the linked Byteball address, which currently is:
: .
Move your bytes to the linked address in order to maximize the amount of blackbytes you receive.
Move your bytes to the linked address in order to maximize the amount of blackbytes you receive.
However, the ammount of GB it shows, is less than I have in my wallet in the actual address.
Am I missing anything? Are there some kind of "change addresses" where BB goes to when I make transactions? I would appreciate your help. TY!
Exactly, like in bitcoin, some bytes are transferred to change addresses when you do an outgoing tx. So best practice is to send your complete balance to yourself, using the address you've linked in the transition chat.
in this situation i have to send all bytes from address_1 to address_2 and then back to address_1 where:
address_1 – is linked to my btc and has problems (bot shows lower balance than it is actually);
address_2 – additional address within the same wallet.
am i gettin' this right?
Send it to address_1.
You can find all used addresses in the cogwheel menue under Advanced/Wallet Information.
i used only this one address_1 to all transactions and the difference between real balance and shown by bot info is near 2 %.
upd. solution:
i've had the same issue with my btc address (difference between blockchain.info and current btc address balance) and as i said above – byteball bot shows lower balance than it's actually is.
cure:
1. move all ur btc to the new btc address within ur btc wallet
2. move all ur bb to the new bb address within ur bb wallet
3. chat with the transition bot and link new btc address and new bb address (for examle via signing message in the btc core wallet).
worked for me fine.
the bot's info is correct now. ☺
Jump to: