Bitcoin Forum
August 25, 2019, 09:05:05 PM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 [37] 38 39 40 41 42 43 44 45 »
721  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 18, 2016, 03:01:46 PM

Good job! Thank you!
722  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 18, 2016, 12:26:39 AM
What is the likely date for the BTC to be in our wallets and the airdrop generally. I highly recommend it's pushed back to around Christmas....even make it a New Years end date. Why? Because there isn't enough people who know about this project so it risks an uneven distribution and less interest of only a small number of people have heard of it.


The developer should do a poll to see the kind of numbers of people who are aware of this airdrop....I bet you it's less than 1000.

The ANN is only 12 days old and you have already found the way to this thread! Wink There is more than a month, maybe two, left for everybody and his dog to learn about Byteball! This thread is not the only marketing effort, there are several tweets already, also threads in other crypto forums, and I know about some bloggers, who will release something in the next days.

So nothing to worry about, Byteball will be well-known when the initial distribution happens.

Sounds a bit like Cryptkeeper wants to keep all the crypto for himself.

The strength as the developer has said is in the widely held distribution. At this point it's I bet known about by a few hundred people at best, alts is a very small world compared to Bitcoin and also there are so many projects these days even a dedicated alt coin investor can easily miss this free offer. If the distribution ends up in less than 1000 wallets this coin is DOA. What's a few more weeks in the grand scheme of things?

We all benefit from network effects when the distribution is as wide as possible.  Your suggestion heard, but at this time it is just too early to change plans.
723  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 18, 2016, 12:23:46 AM
hi
how to solve this problem?
http://i64.tinypic.com/21cti7n.png

This is a known bug that will be fixed in the next release.  It is caused by incorrect behavior after you have deleted the wallet seed.
Before the next release, you can reinstall the app (you will lose all testbytes) but don't try delete the seed in the current version.
724  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 17, 2016, 12:22:06 AM
where can we buy some coins

I'm afraid nobody will sell, get free testbytes from the faucet.
725  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 17, 2016, 12:18:23 AM
This worked well when I paired both my phone and my desktop, however pairing two of my desktop apps didn't work. I copied the pairing code from device1 and emailed it to myself, I then added it as a new device on device2, however, device1 appears with the name New (in device2's list of paired devices), whereas it should've been the name device1 was configured with.
The name should update when device1 comes online.

Thank you for spotting, will investigate.
Do you need the amounts?
No, thanks, I already see the symptoms.

After pairing my phone with my desktop, I requested a payment from the phone, when I clicked to execute the payment from my desktop, my phone displayed this error: http://imgur.com/a/Riafp. And now it is displayed each time I start the app.
Please update to 0.3.1.

Also, when I was trying to send CryptKeeper some blackbytes (upon their request), This error appeared: https://imgur.com/a/0cMcO. Then after some minutes, I was able to send.
This is normal, one of previous payments was not confirmed yet.
726  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 17, 2016, 12:10:47 AM
i have some problem to sync the wallet! did works fine tille 2 days ago!

What kind of problem, what platform?
727  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 16, 2016, 04:26:59 PM
New version 0.3.1 released for Android, it fixes crashes when receiving blackbytes.
The new version is already in Google Play, please update if you don't have auto-updates.

Desktop clients were not affected by these bugs, you don't need to upgrade them.
728  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 16, 2016, 03:46:11 PM
I've noticed that the chat history is deleted when I restart the wallet.
I suggest to store the history locally, you can add a delete button to clear it.

Yes, I agree.  Or, for simplicity of display, show the last 10 messages and have a History section, sorted by date in Descending order.

Well, it was not designed as chat app but is probably becoming that.
Before we implement local storage of chat history, the auto-deleting history is a privacy feature.
729  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 15, 2016, 06:04:37 PM
sorry can some one explain.this sounds great but if transactions are not stored on blockchain , does that mean both sender and reciever need to be online at the same time???

They don't need that.  Private information is delivered through a hub, which stores it while the recipient is offline (similar to email).  The information is end-to-end encrypted, so even the hub can't see it.

thank you for making it clear for me. It is all writen in Javascript. Do you not see problems with security?

I would say rather the opposite.  One common source of mistakes is manual memory management.  In Javascript, developers don't have to care about that, therefore the risks are reduced.
730  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 15, 2016, 03:36:43 PM
I started a new thread https://bitcointalk.org/index.php?topic=1617816.0 to discuss the smart contract language used in Byteball.

Unlike most other smart contract languages, the one we use is declarative, which allows it to very clearly communicate the intent of the author.  Although it is not as powerful as Ethereum's Solidity, the clarity of the language ensures that the contract operates as expected, and something like TheDAO disaster becomes almost impossible.

Twitter: https://twitter.com/ByteballOrg/status/776440221122433024
731  Alternate cryptocurrencies / Altcoin Discussion / Declarative smart contracts in Byteball on: September 15, 2016, 03:00:01 PM
When you entrust your money to a smart contract, you want to be absolutely sure that the contract operates as you expect (remember TheDAO?).  One way to achieve this is by having a smart contract language that is designed to express what the contract expects, rather than how it accomplishes its goals.  This is exactly what declarative languages do.

The purpose of this post is to introduce the declarative smart contract language I chose for Byteball, the cryptocurrency I recently launched.  The language is designed to be as easy to understand as possible, so that even non-developer can immediately see what a contract means by just looking at its code.  The language values clarity over power and it is not as powerful as Ethereum's Solidity.  It is not turing-complete, and you cannot write even 'Hello world' program in this language.  But it is able to solve many practical business tasks.

Money in Byteball are stored on addresses.  Address is just a hash (plus checksum) of an address definition, and the address definition is an expression in the Byteball smart contract language that evaluates to either true or false.

Here is an example of the simplest address definition that defines an address controlled by a single private key:

["sig",{"pubkey":"Ald9tkgiUZQQ1djpZgv2ez7xf1ZvYAsTLhudhvn0931w"}]

The pubkey above is base64-encoded public key.  The expression evaluates to true if the signature provided with the transaction is valid and produced by the private key that corresponds to the above public key.  The address (checksummed hash in base32) corresponding to this definition is A2WWHN7755YZVMXCBLMFWRSLKSZJN3FU.

All expressions in this language evaluate to a boolean value, and multiple boolean subexpressions can be combined using boolean operators.  For example, this is a definition that requires two signatures:

["and", [
  ["sig", {pubkey: "one pubkey in base64"}],
  ["sig", {pubkey: "another pubkey in base64"}]
]]

To spend funds from the address equal to the hash of the above definition, one would need to provide two signatures.

As you noticed, we use JSON to construct the language expressions.  This is an unusual choice but allows to use existing well-debugged, well-supported, and well-optimized JSON parsers rather than invent our own.

"Or" condition can be used to require signatures by any one of the listed public keys:

["or", [
  ["sig", {pubkey: "laptop pubkey"}],
  ["sig", {pubkey: "smartphone pubkey"}],
  ["sig", {pubkey: "tablet pubkey"}]
]]

The above is useful when you want to control the same address from any of the 3 devices: your laptop, your phone, and your tablet.

The conditions can be nested:

["and", [
  ["or", [
    ["sig", {pubkey: "laptop pubkey"}],
    ["sig", {pubkey: "tablet pubkey"}]
  ]],
  ["sig", {pubkey: "smartphone pubkey"}]
]]

A definition can require a minimum number of conditions to be true out of a larger set, for example, a 2-of-3 signature:

["r of set", {
  required: 2,
  set: [
    ["sig", {pubkey: "laptop pubkey"}],
    ["sig", {pubkey: "smartphone pubkey"}],
    ["sig", {pubkey: "tablet pubkey"}]
  ]
}]

("r" stands for "required") which features both the security of two mandatory signatures and the reliability, so that in case one of the keys is lost, the address is still usable and can be used to change its definition and replace the lost 3rd key with a new one.

Also, different conditions can be given different weights, of which a minimum is required:

["weighted and", {
  required: 50,
  set: [
    {weight: 40, value: ["sig", {pubkey: "CEO pubkey"}] },
    {weight: 20, value: ["sig", {pubkey: "COO pubkey"}] },
    {weight: 20, value: ["sig", {pubkey: "CFO pubkey"}] },
    {weight: 20, value: ["sig", {pubkey: "CTO pubkey"}] }
  ]
}]

A definition can contain reference to another address:

["and", [
  ["address", "ADDRESS 1 IN BASE32"],
  ["address", "ADDRESS 2 IN BASE32"]
]]

which delegates signing to another address and is useful for building shared control addresses (addresses controlled by several users).  This syntax gives the users the flexibility to change definitions of their own component addresses whenever they like, without bothering the other user.

A subdefinition may require that the transaction be cosigned by another address:

["cosigned by", "ANOTHER ADDRESS IN BASE32"]

One very useful condition can be used to make queries about data previously stored in Byteball:

["in data feed", [
  ["ADDRESS1", "ADDRESS2", Ö],
  "data feed name",
  "=",
  "expected value"
]]

This condition evaluates to true if there is at least one previous message stored in Byteball database that has "data feed name" equal to "expected value".  The data feed must be posted to Byteball decentralized database by one of the oracles whose addresses are "ADDRESS1", "ADDRESS2", ...  Since oracles post to the common database, we call them on-chain oracles.

On-chain oracles are a very powerful thing indeed.  For example, this address definition represents a binary option:

["or", [
  ["and", [
    ["address", "ADDRESS 1"],
    ["in data feed", [["EXCHANGE ADDRESS"], "EURUSD", ">", "1.1500"]]
  ]],
  ["and", [
    ["address", "ADDRESS 2"],
    ["in data feed", [["TIMESTAMPER ADDRESS"], "datetime", ">", "2016-10-01 00:00:00"]]
  ]]
]]

It relies on two oracles, one is posting EUR/USD exchange rate, the other is posting the current time.  Initially, the two parties fund the address defined by this definition by sending their respective stakes to the address.  Then if the EUR/USD exchange rate published by the exchange address ever exceeds 1.1500, the first party can sweep the funds.  If this doesnít happen before Oct 1, 2016 and the timestamping oracle posts any later date, the second party can sweep all the funds stored on this address.

Another example would be a customer who buys goods from a merchant but he doesnít quite trust that merchant and wants his money back in case the goods are not delivered.  The customer pays to a shared address defined by:

["or", [
  ["and", [
    ["address", "MERCHANT ADDRESS"],
    ["in data feed", [["FEDEX ADDRESS"], "tracking", "=", "123456"]]
  ]],
  ["and", [
    ["address", "BUYER ADDRESS"],
    ["in data feed", [["TIMESTAMPER ADDRESS"], "datetime", ">", "2016-10-01 00:00:00"]]
  ]]
]]

The definition depends on the FedEx oracle that posts tracking numbers of all successfully delivered shipments.  If the shipment is delivered, the merchant will be able to unlock the money using the first condition.  If it is not delivered before the specified date, the customer can take his money back.  This example is somewhat crazy because it requires FedEx to post each and every shipment.  See the white paper for a more practical way to achieve the same result.

A definition can also include queries about the transaction itself, which can be used for example to code limit orders on a decentralized exchange.  Assume that a user wants to buy 1,200 units of some asset for which he is willing to pay no more than 1,000 bytes (the native currency of Byteball).  Also, he is not willing to stay online all the time while he is waiting for a seller.  He would rather just post an order at an exchange and let it execute when a matching seller comes along.  He can create a limit order by sending 1,000 bytes to an address defined by this definition:

["or", [
  ["address", "USER ADDRESS"],
  ["and", [
    ["address", "EXCHANGE ADDRESS"],
    ["has", {
      what: "output",
      asset: "ID of alternative asset",
      amount_at_least: 1200,
      address: "USER ADDRESS"
    }]
  ]]
]]

The first or-alternative lets the user take back his bytes whenever he likes, thus cancelling the order.  The second alternative delegates the exchange the right to spend the funds, provided that another output on the same transaction pays at least 1,200 units of the other asset to the userís address.  The exchange would publicly list the order, a seller would find it, compose a transaction that exchanges assets, and sign it together with the exchange.  Note that the exchange does not receive arbitrary control over the user's funds, it can spend them only if it simultaneously pays the alternative asset to the user, while the user retains full control over his funds and can withdraw them from the contract when he likes.

You can combine the above and a few other boolean constructs (see the white paper) to encode many of the clauses you are likely to see in real-life legal contracts.  And the language is clear, straightforward, and it directly expresses the intent of the contract parties.

This language is already used in Byteball, you can view the source code and create tools that make use of the language.




732  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 15, 2016, 09:35:14 AM
I've chatted with kaicrypzen via byteball and sent him a payment request.
The appearance in the chat view could be improved, it looks like this:


On his end (the first, short line) it looks quite good, but on my end it looks kind of garbled.
IMO it would be good to add some descriptive text like "click on this to pay".

On his (receiver) end it is a link, it's clickable.
On your (requestor) end you see the source code of the payment request link, I agree we might show only the human readable text instead, but it shouldn't be clickable.
733  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 15, 2016, 09:14:06 AM
If you are interested in pairing devices, here is my pairing code:
Code:
AmOIR5s+WxMyYUhUbEUwvr4lSP68ftSd9My8vJ1Esz2/@byteball.org/bb#gnSZxT7d0S2R

Remember, this is for one-time use, the code won't work for the second person.

I actually tried pairing two of my devices by adding the pairing code from one to the other but this doesn't seem to be enough (I chatted from one device to another but never received messages), maybe I need to perform the operation on both devices? or maybe both must be online?
It is enough.  If the devices are listed in each other's list of paired devices, they should be able to chat.

Some observations:
- 0 is considered as a valid amount, I mean when I type 0, Not valid does not appear (whereas it appears for -1 for instance), however 0 does not trigger the SEND button (which is normal), so maybe 0 should be considered not valid.
Agreed, a minor glitch.

Quote
- When writing a very long number the digits overlap on bytes.
That's a really long number, are you a whale? Smiley

Quote
- I tried sending very large numbers and it resulted in sending 1 or 2 bytes.
Thank you for spotting, will investigate.

Quote
- Why is it compulsory to backup the wallet keys before receiving a payment?
Actually, it shouldn't be compulsory, I copied it from Copay and didn't change.  Will fix.
734  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 15, 2016, 08:44:27 AM
What I've found so far with the windows binary is that the installer appears to work, but launching the wallet fails after that. Going to try the following:
1. backup my C:\Users\...\AppData\Local\byteball-test
2. Delete the folder above
3. Reinstall using the binary
4. Attempt to reload my wallet from the backup.

And how step to backup via android device?

Unfortunately, the usual methods of backup don't work for Byteball.  This is because of private payments, which are stored only in your local database and cannot be restored from a seed.  Desktop users can backup the entire app data folder C:\Users\...\AppData\Local\byteball-test but you have to do it every time you send or receive blackbytes (or any other private asset), which is not something I would recommend.

The right way to protect your funds against loss is to create a multisig wallet.  Any wallet with redundancy will do, e.g. 1-of-2, 2-of-3, 1-of-3.  With multisig, if any of your devices is lost or fails, you'll be able to use the remaining devices to move the funds to a new wallet.
735  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 14, 2016, 07:42:26 PM
sorry can some one explain.this sounds great but if transactions are not stored on blockchain , does that mean both sender and reciever need to be online at the same time???

They don't need that.  Private information is delivered through a hub, which stores it while the recipient is offline (similar to email).  The information is end-to-end encrypted, so even the hub can't see it.
736  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 14, 2016, 07:20:49 AM
any wallet for win 32 dev?
I have already download but win 64.
its not compatibel for 32bits.  Angry

Try this: https://byteball.org/downloads/Byteball-test-win32.exe.
This 32bit version works on my win64, you will be the first to try it in win32.

Has this been proven to work?
Tried installing it and seem not. It prompts for awhile then just disappears after. If anyone experienced such do let us know how it works.

Do you say the _installer_ fails?  Please PM me with as many details as possible.
737  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 13, 2016, 05:58:31 PM
Version 0.3.0 is released https://github.com/byteball/byteball/releases/tag/v0.3.0.

Several bugs were fixed, in particular:
- receiving long chains of private payments in light wallets (thank you Bitsharesuser1234 and CryptKeeper for help in discovering the issue)
- opening byteball: links when the wallet is encrypted by password
- receiving private payments sometimes was not displayed in chat window

Please upgrade your desktop clients.  Android should have already updated automatically by this time (although I still receive crash reports from someone who is using the original version on Android, please update).

There are still some bugs whose cause is unclear to me, I need more data because the bugs are rare.  Please actively use the wallet, use it in the least evident way you can think of, trying to cause the bugs to surface.  If you see something unexpected, please report.
738  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 13, 2016, 05:28:24 PM
whether android wallet can be used when the coin is official and not a test ? because I prefer to use android wallet that does not consume a lot of space in my computer files .

Of course, it will be used on livenet too.
739  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 13, 2016, 04:43:27 PM
Having both options adds complexity on both technical and usability sides:
1.  More code that needs to be written, debugged, and tested.  Despite all the testing, more code is always more complexity and greater probability of errors, including security errors.  Complexity is the enemy of security.
2.  More options for users means more options for attackers too.  This needs to be analyzed, and with growing complexity the chances of missing something increase.
3.  Longer instructions for users.  They are scared off by the abundance of text or unfamiliar words, like "signing a message".
4.  Users have to evaluate both options and make their choices.  Choice is difficult when the difference between the choices is not immediately clear.

All this is fine as long as there is a real tangible benefit in adding more options that overweights the negatives.  In this particular case, there isn't.

Thx for clarifying these points. Points 3 and 4 are okay but as I said earlier they do not apply to all users, I think we won't reach an agreement on that and that's okay Smiley.

What I find negative about this, is the lack of options ... (I want to send a signed message to claim, I can't. I want to see the transaction id and/or fees before sending, I can't. I don't want to use Google Play Smiley, I can't).

Looks like you want more control than an average user (well, as I perceive an average user).  That's OK, there is no one size that fits all.  I envisage that we'll have multiple wallets in Byteball ecosystem that fit different preferences, like we already have in Bitcoin.
740  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments on: September 13, 2016, 01:45:25 PM
A good idea if you want to maximize distribution would be to not only extend the period, but find a way to make linking accounts available as soon as possible. This way, people don't have to wait another 1 - 2 months until they can link their accounts and potentially forget or miss byteball.

A good way would be some kind of newsletter to keep people informed so they don`t miss everything.

Follow the project's twitter https://twitter.com/ByteballOrg.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 [37] 38 39 40 41 42 43 44 45 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!