|
The 4th round of distribution is complete.
Total 22,834.307841319 GB distributed, new available supply is 160,276.688294257 GB.
43,654.114908786 GBB distributed to the linked addresses.
4,551.392375023 GBB transferred to the community fund.
The 5th round is scheduled for the full moon of May (May 10, 2017 at 21:42 UTC), the rules stay the same:
BTC to bytes: 1 BTC of proven balance gives you 62.5 MB (0.0625 GB)
BTC to blackbytes: 1 BTC of proven balance gives you 2.1111 * 62.5 million blackbytes (money supply of blackbytes is 2.1111 times more than that of bytes)
Bytes to bytes: 1 byte on any Byteball address gives you 0.1 new bytes
Bytes to blackbytes: 1 byte on linked Byteball address gives you 0.21111 blackbytes
Get ready for the 5th round when Byteball will be even better than now!
|
|
|
|
Hello
I have this message when i try to send blackbytes through chat to another wallet:
"Impossible to send payment
conflicting spend proof in inner unit"
Even with version 1.7, the problem still exist.
Thank you if you have somme help!
I will reward the first who will help me to solve this issue with 24 GBB (~ $100).
The error means you were trying to double-spend. This might happen if you are running the same wallet (same seed) on more than one device. |
|
|
|
I tried engaging the transition bot and it just echos whatever I say. Does that mean I'm too late? Or that the bot is temporarily offline?
The transition bot will be resumed after the distribution finishes. |
|
|
|
Version 1.7.1 released https://github.com/byteball/byteball/releases. Upgrade is mandatory for full nodes. This release fixes the bug "known bad 3CxaZ7iziNbFjbif9O8bSmKbtXK6RDEbdKuoBmnig1s=" that was posted above. Also in this update: * improved French translation * fixed a bug that could cause an infinite cycle and make the app unresponsive The update is only for desktop, as the bug affects only full clients. The distribution of blackbytes is still under way, I'll update you when it is finished (hopefully soon). |
|
|
|
Getting the follow error from 1.7 wallet (on mac):
Uncaught exception: Error: Error:
malformed SELECT hash_tree_balls.unit FROM
hash_tree_balls LEFT JOIN units USING(unit) WHERE
units.unit IS NULL ORDER BY ball_index
Screenshot: https://snag.gy/PUn5Vb.jpgWallet then crashes. Any ideas on how I can resolve this? Make sure that the disk is not full and there are no hardware problems. Try restarting the wallet. If nothing helps, this might be one of those unfortunate cases when you have to use a backup. |
|
|
|
Do I misunderstand or are you sprouting out bs scenarios?
If I get the whitepaper correctly then in the mentioned scenario (everyone picked themself as the new witness) we'll get the DAG looking like this:  There is a chance I've got the whitepaper wrong, of course. So far noone has explained what will happen. It looks nice but won't happen. Odrak explained this above by quoting the whitepaper: Incompatible parents are still permitted, but they have no chance of becoming best parent. which means that such units will not be on the main chain but they still get descendants and get confirmed. |
|
|
|
I love thisproject however I have a problem with the witnesses choose mecanism, aka "12 catpains of industry" or well reputed equivalent.
First (and biggest one) : who is to coopte such "captains". In a supposed decentralysed network it means a central authority somewhere or at least a consensus voting system.
Second : what if no such "captain of industry" joins in? Should we bless project founders for eternity ? (we all die some day).
Three : 12 is a too limited number. This is intentionaly set so that we can humanely follow the witnesses quality. But I do not want to ask periodicaly myself whereas witnesses are good quality or not. I just want to feel confident with the network any time.
I would suggest the following :
- no more limited witnesses number
- all wallets could optionnaly run as witnesses
- if a end-user wishes to act as a witness is has to back some "good" amount of GBYTE (prevent spam and initial amount for serial post).
- each time a witness serial post he is awarded more than its post cost (aka end users are prone to become witnesses for profit)
- wallets choose their witnesses in a hard-coded random fashion among all witnesses pool.
First of all, I remind you that following the witness lists of "captains of industry" is just a suggestion how witness lists could be updated, it is not a protocol-level thing. That said, I don't think the question of captains of industry is that hard. If you ask me about captains of auto industry today, I would name GM, Ford, Toyota, Renault, Michelin, and a few others. In Bitcoin industry today: AlphaBay, Coinbase, Localbitcoins, Overstock, Polo, and a few others. But I do not want to ask periodicaly myself whereas witnesses are good quality or not. You don't have to. If you don't want to or feel unable to make decisions yourself in this particular area, you can always follow the opinion of someone you trust. To clarify, there is no such thing as "wish to act as a witness", you can only "wish to be named as a witness". Anyone can be named a witness by anyone. The above was 100% human, 0% technical. Regarding suggested protocol changes, all such changes should be carefully analyzed with respect to potential consequences, in particular whether they could lead to consensus failures such as forks and deadlocks. |
|
|
|
I was missing here for some time... Sorry if this is answered somewhere down the thread - my question is whether it is possible to trade Bytes vs BlackBytes using the trading bot? Trading bot seems to be the best place for such functionality, I suppose it should be there, but cannot find it by some reason... 
On different topic: @tonych - you are awesome. Though, well... I think you know that already  Welcome back Trading is possible, no bots, just peer-to-peer: https://medium.com/byteball/making-p2p-great-again-fe9e20546a4a |
|
|
|
Now you can also P2P gamble using smart contracts.  The oracle FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH (which also monitors Bitcoin blockchain) posts pseudorandom numbers derived from Bitcoin block hash. A new number is posted every time a new Bitcoin block is mined and gets one further confirmation. The random numbers are posted under data feed name randomXXXXXX where XXXXXX is Bitcoin block number. The numbers are between 1 and 100,000. You can bet on a future random number being less than or greater than a specific value, for example, there is 25% chance that the number will be below 25,000 and 75% chance that it'll be above 25,000. The above contract was between my Mac and my phone, it was created before block 460852. This is the data feed that was posted by the oracle after this block was mined: https://explorer.byteball.org/#Ns//o52EKR32ykuHfUfcm3ailHtta6TvM5kB07vbpVA=bitcoin_hash: 0000000000000000019dd457cf8e233701dab44ac855492d575a4366556213e0 bitcoin_height: 460852 bitcoin_merkle: GW9cQW5m0KLIi2suUlkzRP2yurg8jLEax3uHiun7kik= random460852: 3478934789 is more than 25000, the Mac won. Join #gambling channel on our Slack http://slack.byteball.org/ to find a partner for P2P dice game. P.S. And we didn't need to do a $2m ICO to organize this simple game. |
|
|
|
From the blog Now you can short any coin without owning it, simply by betting that its price goes below certain level. Being a binary option, this contract also limits your loss (you can’t lose more than you paid) and includes an implicit take-profit (no risks after the price breaks the set level). You can actually do better than this with price oracles. You can issue collateralized loans. You can peg a token to any real world asset or basket of assets by backing it with equivalent amount of collateral in bytes or other crypto. I guess there is some trust involved that the collateral holder won't run away with the collateral? Collateral can be locked by smart contract, just like bitshares does. OK, assuming the collateral is locked by a smart contract, I wonder how it can be guaranteed that there is enough collateral even if the price of the real-world asset rises 10x. There is a minimum collateral defined by maintenance collateral ratio. When collateral value drops below this ratio, position gets margin called by a smart contract. There is no 100% guarantee against black swan event (when collateral value goes to shit instantly), but risk of such event can be reduced by setting high enough MCR. This works in practice on bitshares DEX. Everything works pretty much similar to how brokerage firms do it, but implemented through a smart contract. Does it mean there is trade-off between being overcollaterized (thus wasting capital) and bearing the risk of margin call? What brokerage firms do seems like the opposite: they lend you 100x of what they hold in collateral, thus increasing money supply. position gets margin called by a smart contract Byteball smart contracts are just constraints. They just tell you the conditions when this contract can be spent. They can't sell a position. This also assumes presence of a market which is not a protocol-level thing. |
|
|
|
From the blog Now you can short any coin without owning it, simply by betting that its price goes below certain level. Being a binary option, this contract also limits your loss (you can’t lose more than you paid) and includes an implicit take-profit (no risks after the price breaks the set level). You can actually do better than this with price oracles. You can issue collateralized loans. You can peg a token to any real world asset or basket of assets by backing it with equivalent amount of collateral in bytes or other crypto. I guess there is some trust involved that the collateral holder won't run away with the collateral? Collateral can be locked by smart contract, just like bitshares does. OK, assuming the collateral is locked by a smart contract, I wonder how it can be guaranteed that there is enough collateral even if the price of the real-world asset rises 10x. |
|
|
|
From the blog Now you can short any coin without owning it, simply by betting that its price goes below certain level. Being a binary option, this contract also limits your loss (you can’t lose more than you paid) and includes an implicit take-profit (no risks after the price breaks the set level). You can actually do better than this with price oracles. You can issue collateralized loans. You can peg a token to any real world asset or basket of assets by backing it with equivalent amount of collateral in bytes or other crypto. I guess there is some trust involved that the collateral holder won't run away with the collateral? |
|
|
|
What is the pairing code of the CoinMarketCap oracle?
It doesn't accept pairing requests. What for? |
|
|
|
I am just playing a little bit around with Byteball and I am wondering if there is an API I can use to access DAG data on localhost? Couldn't find any information on the web.
There is no documentation yet but you can read the DAG data by accessing the sqlite database directly. You can learn something about its structure from https://github.com/byteball/byteballcore/blob/master/byteball-sqlite.sql |
|
|
|
Do I understand this correctly that to use this betting feature one must find:
1. some other user eager to be a counterparty to the betting contract
2. find out the other user's device address
3. pair the wallet with the other user's device
4. start a chat and set up a contract as described in the medium post
If that's correct we need some community forums to find possible counterparty users to bet with.
Correct. (2) and (3) is achieved by exchanging a pairing code. |
|
|
|
Version 1.7.0 released https://github.com/byteball/byteball/releasesThis version enables prediction markets based on P2P smart contracts. See https://medium.com/byteball/making-p2p-great-again-episode-iii-prediction-markets-f40d49c0abab Now you can bet on (or hedge against) any events and get paid if the event happens. One type of events that is already working today is events based on exchange rates of crypto coins and major fiat currencies. You are welcome to add new oracles that post other real-world events and enable prediction markets based on these events. Other updates: * New translations thanks to community members: Hungarian, Swedish, Polish. Dutch translation improved. * Multiple small improvements and bugfixes If you are running a full wallet, the upgrade is mandatory. The new version extends the smart contract language. As soon as the new language constructs are used for the fist time, old nodes will not recognize them and will be stuck until upgraded. |
|
|
|
i syn 50%, and i close the wallet,net time when i open the wallet,it start from 0% to syn,why?
It is normal, the % shows the percentage of the work left. |
|
|
|
this only works if the payload hash stays the same for each anonymous partner does it not? Otherwise, it would just be a chain of nonsense hashes that could claim to contain anything. A user could collude with themselves and spread fake funds over many accounts with data that is apparently okay as the new recipient can't confirm or deny the validity of previous transactions. It doesn't seem like it would be easy to hide data because the spending transaction needs to get change as well which would have to be public to know quantity.
If the payload hash is always the same i guess it makes sense however it would not allow coins to be subdivided would it not be similar to minting a coin? Also when the data becomes non-private it would be easy to expose everyone involved.
The recipient receives the entire history of the coin and can verify that it is valid, as well as verify that the payload does hash to the correct value. |
|
|
|
|
Show Posts
