Quote from: CryptKeeper on September 11, 2016, 02:05:26 PM

If you want to test drive the wallet, you can post your byteball address here and I will send you some bytes! Grin

Here are my addresses:
KYZN4SPSZAUN2SEO4JZ2F5PEHQEXYC5S
byteball:KYZN4SPSZAUN2SEO4JZ2F5PEHQEXYC5S

DSZ6HWO6VWSQUCI67PIN27HL4LYYK5JV
byteball:DSZ6HWO6VWSQUCI67PIN27HL4LYYK5JV

CryptKeeper, I sent 111 bytes to the first address and 999 bytes to the second, did you receive them? Both transactions cost 589 bytes, does this mean that the fee is set to this amount whatever the number of bytes one sends? What about this:

Quote from: tonych on September 05, 2016, 04:00:28 PM

The fees paid for storing ones transactions (or any other data) in the Byteball database are equal to the size of the data being stored. If your transaction size is 500 bytes, you pay exactly 500 bytes (the native currency of Byteball) in fees.

Quote from: tonych on September 05, 2016, 04:00:28 PM

The fees are collected partially by those who are first to reference your transaction as parent and partially by witnesses.

So, anyone here who got the fees?

Is there any way to have more information about a transaction, the id for instance, the number of confirmations it needed (it just goes from unconfirmed to cofirmed)?

Quote from: tonych on September 11, 2016, 04:40:47 PM

Quote from: Fragbait on September 11, 2016, 03:48:50 PM

or

b) require a signed message from the claiming address instead of making a 0.001 BTC transaction
- then people wouldn't have to make a tx that possibly compromises their privacy or loses them coins

This one is complex too. Not every wallet has this function, and even when it has, users rarely know how to use it. There is nothing simpler than just regular payment, which is the basic functionality of every wallet.

Can't we have both? Users who know how to/can/want to sign a message may do so and others may send a payment.