Quote from: byteball3r on February 05, 2018, 06:07:59 PM

No, these are reasonable users that the project is driving away by being asinine. Why on earth should users not be refunded when a project-sponsored verification fails do to technical reasons? And why is it a goal of this project to make everything user-unfriendly as possible while making public no plans for improvement? The market's trust in this project is fading because of poor leadership attitudes and I say that as someone with a lot of GB. Tony doesn't seem to care about the price of GB nor the market perception, saying exchanges and "traders" are unnecessary.

Also, will there or will there not be an aidrop in March? What will happen with all the remaining bytes?

Tony seems to care more about the project than the price. I agree. He wants the project to work (as I see it). So, if the project succeeds, then the price will come.
Everyone is upset with the price; however, the price has tanked on everything - Everything. So, be sure to look relatively at other coins as well.

Quote from: Cent21 on February 06, 2018, 08:24:55 PM

Quote from: shinjikun on February 06, 2018, 08:10:29 PM

Quote from: Cent21 on February 06, 2018, 07:42:58 PM

Hi guys. I need help.

I installed the byteball wallet from play store. I'm not sure but i think it didn't ask me if i wanted a light or a full wallet at start, and now it keep saying syncing.....

Do the android app default to a full wallet? I want a light wallet cause my android device can't contain the entire byteball blockchain.

What i did wrong?

Thanks.

This must be another problem. There is no full wallet for Android.

Thanks for your reply.

I've found an open issue that could be the one i'm experiencing: https://github.com/byteball/byteball/issues/266

My situation is very similar cause i sent some blackbytes to the android wallet that can't sync.

Don't know what to do. If someone have hints please help.

Only lite wallet for android/ios.

If you can't sync, then you likely have TOR or some other feature installed which is blocking communication with byteball servers.

If your wallet shows syncing private payments, then it will need to be fixed. You can send me the wallet and I will fix it for you.
- No, I will not go through the process via chat/dm.

If you have 0 bytes and 0 blackbytes then you don't have the above issue issue with a wallet that is trying to sync private payments.

Quote from: cryptocortex on February 06, 2018, 10:41:27 AM

Quote from: Hyena on February 06, 2018, 08:57:12 AM

Quote from: redhorse on February 06, 2018, 08:41:45 AM

Question regarding the Airdrop:
I've moved my BTC to a segwit address (starting with 3..). The chatbot gives me the following response:

Quote

Only P2PKH addresses (those that start with 1) can sign messages. You can prove ownership of xyz only by microtransaction.

My question is: How can I make such a transaction? What is the address that I've to send to?
Has anyone successfully registered a segwit address with a micro transaction and can give me some guidance? I've checked the Byteball Wiki but couldn't find the answer there.

Segwit addresses are not supported because SegWitCoin is not Bitcoin. You have to use a regular Bitcoin address for linking (the one starting with 1... ).

I have not seen Tony declare something against SegWit.
AFAIK, the reason for SegWit addresses not being supported has something to do with infrastructure in the new Bitcoin network, which at the present moment does not allow sign message.

Tony has nothing against SegWit.
Quite simply, you can't sign a transaction with the transition bot with a segwit address. No signature.

If your intent is to claim bytes for a distribution, then move your coins to a legacy address just prior to the snapshot in order to get your claim. There is another trick is making a transaction from your sw address, and sign via your legacy so that the bot will see both addresses as valid. Sorry, I don't use SW, so I don't have an example to show you.