*Why I Stopped Using Cryptox.pl and You Should Too*
1. It's unreliable. Their website, bitcoin wallet, and Byteball wallet are all flaky.
I needed to sell some bytes for bitcoin one day and my deposit never showed up the entire day. So, essentially my coins were lost when I needed them the most. Of course the price also went down during that time, screwing me more. I contacted @grzem and he was just a total jerk, acting like what happened didn't matter, "and just wait longer" he said.
2. They're greedy. Less than .01 BTC (~$20) is considered dust and will be taken from you if it happens to hit your Cryptox account.
Bitcoin fees are getting crazy and everyone knows it (almost $2 now). So, I was using my Cryptox BTC address as the payout address from the Byteball chatbot exchange. So, when I sold bytes, the BTC would be sent directly to my Cryptox account, and I could buy more bytes. But on the chatbot, you don't control how much someone buys from your order, so small BTC transactions come out occasionally.
This morning I received some hostile emails from Cryptox staff, prolly grzem himself.
I asked for a URL link to their Terms of Service because I could not find it. They sent me a 1 word reply, "Information." Basically, their crappy site doesn't even have URL's so he cannot link me to one. Now I see that if you click Information in the sidebar (never even looked here because I was only interested in Byteball) and then Fees, then look at the chart Other Fees you will finally see something about BTC Deposit Minimum Transfer Amount .01.
Wait, what? Why would this be under Fees???
3. Now there are better, more trustworthy exchanges to trade bytes.
I'm going to switch to Bittrex and Cryptopia.
4. Did I mention Cryptox staff are jerks?
Ain't nobody got time for that.
Topic: Obyte: Totally new consensus algorithm + private untraceable payments - page 712. (Read 1234286 times)
May 18, 2017, 09:59:49 AM
May 18, 2017, 07:33:03 AM
BB is the most low key project I have seen so far, no ICO fund, only reserve 1% of total supply, the dev is best one.
May 18, 2017, 07:30:26 AM
Is it possible to list blackbytes on exchanges?
No. But you have a channel "trading_blackbytes" on Slack. 
May 18, 2017, 05:38:14 AM
Is it possible to list blackbytes on exchanges?
May 18, 2017, 05:05:58 AM
Would it be possible to send transactions to the wallet via Watsapp, LINE etc?
eg "0.347MB@Joey" ?
eg "0.347MB@Joey" ?
May 18, 2017, 05:03:05 AM
How do I link my btc in my electrum wallet to byteballs? I have already installed the wallet. how do I do it?
May 18, 2017, 04:58:11 AM
Hi Yary,
Very interesting to see someone experiment with these possibilities. It should be easier to get a helpful reply on the slack, there is a channel for technical questions. I have no technical insight.
Very interesting to see someone experiment with these possibilities. It should be easier to get a helpful reply on the slack, there is a channel for technical questions. I have no technical insight.
May 18, 2017, 03:35:11 AM
Byteball on Changelly Instant Exchange!
Buy/Sell GBYTE for Bitcoin, Ethereum or any other crypto.
VISA/Mastercard available!
https://changelly.com/exchange/btc/gbyte
Buy/Sell GBYTE for Bitcoin, Ethereum or any other crypto.
VISA/Mastercard available!
https://changelly.com/exchange/btc/gbyte
Polo, Shapeshift, Exodus and Jaxx next
we should avoid polo
Could get on Kraken, yunbao, or yunbi, prolly pay to list on the chinese ones.
May 18, 2017, 03:27:21 AM
Byteball on Changelly Instant Exchange!
Buy/Sell GBYTE for Bitcoin, Ethereum or any other crypto.
VISA/Mastercard available!
https://changelly.com/exchange/btc/gbyte
Buy/Sell GBYTE for Bitcoin, Ethereum or any other crypto.
VISA/Mastercard available!
https://changelly.com/exchange/btc/gbyte
Polo, Shapeshift, Exodus and Jaxx next
we should avoid polo
May 18, 2017, 02:57:22 AM
Byteball on Changelly Instant Exchange!
Buy/Sell GBYTE for Bitcoin, Ethereum or any other crypto.
VISA/Mastercard available!
https://changelly.com/exchange/btc/gbyte
Buy/Sell GBYTE for Bitcoin, Ethereum or any other crypto.
VISA/Mastercard available!
https://changelly.com/exchange/btc/gbyte
Polo, Shapeshift, Exodus and Jaxx next
May 18, 2017, 02:56:10 AM
Creating an asset in the testnet
Hi all,
I'm a developer struggling to define a new asset in the testnet
These are the steps I already managed to complete:
What I understood from the documentation is that I need to run a command (there is a create_asset.js script in the play directory of headless byteball) in order to create an asset but I got stuck with some errors.
I firstly changed the hub url to the testnet in conf.js:
There seem to be some protocol compatibility problems I can read from the log (though it doesn't stop the client):
I have also encountered a problem pairing my UI client to the headless one, my parallel thread of investigation. The client is operating on the testnet as well and I set up the control_address and payout_address in configuration file (conf.js) as follows (they are the value I read from the UI client);
But the pairing doesn't occur. when I type the pairing code into the UI I get no complaints, but as soon as I start to type commands in the chat I get this message:
My wild guess is that my headless client should have been already registered on the testnet at this point but it hasn't done it yet, maybe because of the protocol incompatibility. But it's just a guess.
Finally I tried to create an asset running node play/create_asset.js with poor results:
At the moment I'm stuck. What am I doing wrong? Does anyone have the same issue or any clue? I would be thankful if you could give an hint.
Best regards,
Yary
Hi all,
I'm a developer struggling to define a new asset in the testnet
These are the steps I already managed to complete:
- Cloning and running the byteball client locally (from the code)
- Exchanging bytes on the livenet and testnet
- Running the byteball-headless client locally
What I understood from the documentation is that I need to run a command (there is a create_asset.js script in the play directory of headless byteball) in order to create an asset but I got stuck with some errors.
I firstly changed the hub url to the testnet in conf.js:
Code:
exports.hub = 'byteball.org/bb-test';
There seem to be some protocol compatibility problems I can read from the log (though it doesn't stop the client):
Quote
SENDING ["justsaying",{"subject":"error","body":"Incompatible versions, mine 1.0, yours 1.0t"}] to wss://byteball.org/bb-test
close event, removing 0: wss://byteball.org/bb-test
close event, removing 0: wss://byteball.org/bb-test
I have also encountered a problem pairing my UI client to the headless one, my parallel thread of investigation. The client is operating on the testnet as well and I set up the control_address and payout_address in configuration file (conf.js) as follows (they are the value I read from the UI client);
Code:
"use strict";
//exports.port = 6611;
//exports.myUrl = 'wss://mydomain.com/bb';
exports.bServeAsHub = false;
exports.bLight = false;
exports.storage = 'sqlite';
exports.hub = 'byteball.org/bb-test';
exports.deviceName = 'TestDevice';
exports.permanent_paring_secret = 'randomstring';
exports.control_addresses = ['0W87676ZG4ZT7AY2QX7C7YEJ5CEORIAF2'];
exports.payout_address = 'BKQXMJDKHC5W2JLMQVT2VEHQUC5WADZZ';
exports.KEYS_FILENAME = 'keys.json';
// where logs are written to (absolute path). Default is log.txt in app data directory
//exports.LOG_FILENAME = '/dev/null';
// this is for runnining RPC service only, see play/rpc_service.js
exports.rpcInterface = '127.0.0.1';
exports.rpcPort = '6332';
console.log('finished headless conf');
But the pairing doesn't occur. when I type the pairing code into the UI I get no complaints, but as soon as I start to type commands in the chat I get this message:
Quote
device with this pubkey is not registered here
My wild guess is that my headless client should have been already registered on the testnet at this point but it hasn't done it yet, maybe because of the protocol incompatibility. But it's just a guess.
Finally I tried to create an asset running node play/create_asset.js with poor results:
Quote
starting network
setDevicePrivateKey
objMyTempDeviceKey not set yet, can't log in
long query took 33ms:
SELECT MAX(lb_units.main_chain_index) AS min_retrievable_mci
FROM units JOIN units AS lb_units ON units.last_ball_unit=lb_units.unit
WHERE units.is_on_main_chain=1 AND units.is_stable=1,
load avg: 0.12890625, 0.291015625, 0.36767578125
no leftovers
outbound peers:
will connect to wss://byteball.org/bb-test
connectToPeer done
my_device_hub not set yet, can't log in
setDeviceName TestDevice
setDeviceHub byteball.org/bb-test
logging in to hub byteball.org/bb-test
outbound peers:
already connecting to wss://byteball.org/bb-test
====== my device address: ****************************************
====== my device pubkey: ****************************************
====== my pairing code: **************************************************************************************************************
/home/ignite/IdeaProjects/headless-byteball/node_modules/byteballcore/my_witnesses.js:32
throw Error("wrong number of my witnesses: "+arrWitnesses.length);
^
Error: wrong number of my witnesses: 0
at Error (native)
at /home/ignite/IdeaProjects/headless-byteball/node_modules/byteballcore/my_witnesses.js:32:10
at /home/ignite/IdeaProjects/headless-byteball/node_modules/byteballcore/sqlite_pool.js:220:5
at Statement. (/home/ignite/IdeaProjects/headless-byteball/node_modules/byteballcore/sqlite_pool.js:113:6)
setDevicePrivateKey
objMyTempDeviceKey not set yet, can't log in
long query took 33ms:
SELECT MAX(lb_units.main_chain_index) AS min_retrievable_mci
FROM units JOIN units AS lb_units ON units.last_ball_unit=lb_units.unit
WHERE units.is_on_main_chain=1 AND units.is_stable=1,
load avg: 0.12890625, 0.291015625, 0.36767578125
no leftovers
outbound peers:
will connect to wss://byteball.org/bb-test
connectToPeer done
my_device_hub not set yet, can't log in
setDeviceName TestDevice
setDeviceHub byteball.org/bb-test
logging in to hub byteball.org/bb-test
outbound peers:
already connecting to wss://byteball.org/bb-test
====== my device address: ****************************************
====== my device pubkey: ****************************************
====== my pairing code: **************************************************************************************************************
/home/ignite/IdeaProjects/headless-byteball/node_modules/byteballcore/my_witnesses.js:32
throw Error("wrong number of my witnesses: "+arrWitnesses.length);
^
Error: wrong number of my witnesses: 0
at Error (native)
at /home/ignite/IdeaProjects/headless-byteball/node_modules/byteballcore/my_witnesses.js:32:10
at /home/ignite/IdeaProjects/headless-byteball/node_modules/byteballcore/sqlite_pool.js:220:5
at Statement.
At the moment I'm stuck. What am I doing wrong? Does anyone have the same issue or any clue? I would be thankful if you could give an hint.
Best regards,
Yary
May 18, 2017, 02:28:39 AM
i have never upgraded my light client.
My version 1.8.2. What should I do to upgrade to 1.8.5?
Is is safe just to push UPGRADE button that pop-ups as client launches?
My version 1.8.2. What should I do to upgrade to 1.8.5?
Is is safe just to push UPGRADE button that pop-ups as client launches?
Yes, it will open your browser to the download page for the new version
May 18, 2017, 02:22:03 AM
i have never upgraded my light client.
My version 1.8.2. What should I do to upgrade to 1.8.5?
Is is safe just to push UPGRADE button that pop-ups as client launches?
My version 1.8.2. What should I do to upgrade to 1.8.5?
Is is safe just to push UPGRADE button that pop-ups as client launches?
May 18, 2017, 02:03:55 AM
I bet you 15BTC that you wont actually fulfill your words, its all empty words, retarded ideas, and no deliveries just like iotacoin.
What words exactly?
PS: If the devs are too busy now to help maybe someone could point me to network protocol description? I'll try to reverse-engineer it to send hand-crafted raw transactions.
May 18, 2017, 01:44:05 AM
Anyone know what it is? This occurs when I run Byteball wallet. Some site was blocked by my virus protection. Seems it links to a malicious website...
It is not related to byteball.wang it is due to the wallet itself. If you downloaded you wallet from byteball.org you can ignore the alert. May 18, 2017, 01:28:15 AM
we need more marketings for byteball i think.
May 18, 2017, 01:20:24 AM
Anyone know what it is? This occurs when I run Byteball wallet. Some site was blocked by my virus protection. Seems it links to a malicious website...
May 18, 2017, 01:12:05 AM
how can people build applications based on byteball ?
we need that i think.
we need that i think.
May 17, 2017, 10:05:25 PM
Although selfishly I am interested in the monetary gain, I think it defeats the purpose of having a coin to replace a currency, in fact part of the original appeal for me to this currency was that it seemed like it could be something that could work as a monetary replacement, not strictly an investment vehicle
May 17, 2017, 05:11:48 PM
Is your witness actually shared by other people?
Who are your cuple of guys? Is the trans-guy also with you? Who is behind this witness, whatever you call it? Why should I trust that you would act fairly and justly after that poor attempt of labeling other hubs as lesser than your own? What other greedy acts would you do in future?
Trans-guy? Well, like, its only a nickname man.Who are your cuple of guys? Is the trans-guy also with you? Who is behind this witness, whatever you call it? Why should I trust that you would act fairly and justly after that poor attempt of labeling other hubs as lesser than your own? What other greedy acts would you do in future?
Chill out a bit.
Let them battle it out, it's keeping the thread bumped, and new investors will notice the project
last time i saw similar thing like this on BCT the coin went 70x lol
Jump to: