Topic: Obyte: Totally new consensus algorithm + private untraceable payments - page 785. (Read 1234271 times)
April 14, 2017, 06:11:43 AM
Any chance of seeing blackbytes on a major exchange at some point? Can it be done with the fact that transactions are anonymous? I feel they are incredibly undervalue at the moment and just as fungible as monero for privacy.
April 14, 2017, 05:28:18 AM
how about change the trading unit to MB ?
GB is too big..
GB is too big..
I think is a good and simple idea to do in the short term
Not agree.. there will be 1 BILLION Mbytes.. the coin will look cheap in a marketing meaning.
I prefer the current measurment ratio 1GB = 10BTC
April 14, 2017, 05:21:33 AM
Maybe someone knows what this error is and how to fix it?
This is witness:
1)
Witnessing failed: not enough spendable funds from KEKYWT35NDA7LA7M23JTXTEZW2U7242I for 488
2)
Witnessing problem: only 0 spendable outputs left, and can not add more
I get this on the mail set in the settings of conf.json
This is witness:
1)
Witnessing failed: not enough spendable funds from KEKYWT35NDA7LA7M23JTXTEZW2U7242I for 488
2)
Witnessing problem: only 0 spendable outputs left, and can not add more
I get this on the mail set in the settings of conf.json
Throw some money into KEKYWT35NDA7LA7M23JTXTEZW2U7242I.
April 14, 2017, 05:09:24 AM
how about change the trading unit to MB ?
GB is too big..
GB is too big..
I think is a good and simple idea to do in the short term
April 14, 2017, 05:07:50 AM
how about change the trading unit to MB ?
GB is too big..
GB is too big..
Indeed, is more room for price increase if is traded in MB.
Agree, I don't see the point in trading GBytes when we can trade MBytes.
GBYTE Price can surpass BTC, thats great PR
If we use TB then it'll instantly do
April 14, 2017, 04:15:22 AM
Why did Bittrex list only GB and not Blackbytes ?
April 14, 2017, 03:42:07 AM
Hmm so I've just opened my Byteball wallet which I synced with my BTC wallet before the 11th April for the drop. Yet I have still received no coins, not sure what I've done wrong 
April 14, 2017, 03:15:38 AM
@tonych
The initial_witnesses array is used only when your hub starts for the first time.
It seems complicated to have witnesses diversity to emerge unless some major industry player claims he is running a witness and asks for adoption. Although the project adoption looks going well it may take some time for this to come.
In the meantime, I beleive we should start to show that the network relies on community independant operated witnesses for at least a portion of the 12 default list (my personnal opinion is 6 over 12).
On the project side: I think it is really important for the mass adoption that independant witnesses now show up (would later be spontaneously replaced by thoses of notorious captain of industry when they come in) to guarantee witnessing diversity.
On the candidate witness side: unless validating, candidate witnesses are just bleeding byte. It comes, soon or later, quite frustrating and leads to discouraging skilled volunteers.
As you know, together with a hub service to the community, I am operating a witness at MEJGDND55XNON7UU3ZKERJIZMMXJTVCV
Would you agree on setting up this witness as a default in byteball.org/bb and in the conf.js files on Github as a first step to diversity? (I personnaly choosed to replace the 12th one starting by UENJ)
Please take a couple of minutes to think about it.
The initial_witnesses array is used only when your hub starts for the first time.
It seems complicated to have witnesses diversity to emerge unless some major industry player claims he is running a witness and asks for adoption. Although the project adoption looks going well it may take some time for this to come.
In the meantime, I beleive we should start to show that the network relies on community independant operated witnesses for at least a portion of the 12 default list (my personnal opinion is 6 over 12).
On the project side: I think it is really important for the mass adoption that independant witnesses now show up (would later be spontaneously replaced by thoses of notorious captain of industry when they come in) to guarantee witnessing diversity.
On the candidate witness side: unless validating, candidate witnesses are just bleeding byte. It comes, soon or later, quite frustrating and leads to discouraging skilled volunteers.
As you know, together with a hub service to the community, I am operating a witness at MEJGDND55XNON7UU3ZKERJIZMMXJTVCV
Would you agree on setting up this witness as a default in byteball.org/bb and in the conf.js files on Github as a first step to diversity? (I personnaly choosed to replace the 12th one starting by UENJ)
Please take a couple of minutes to think about it.
April 14, 2017, 02:36:44 AM
But where was the easter egg?
April 14, 2017, 02:35:14 AM
how about change the trading unit to MB ?
GB is too big..
GB is too big..
Indeed, is more room for price increase if is traded in MB.
Agree, I don't see the point in trading GBytes when we can trade MBytes.
GBYTE Price can surpass BTC, thats great PR
April 14, 2017, 02:23:05 AM
First Easter Egg found: https://twitter.com/CryptKeeperBTT/status/852766380013215745
April 14, 2017, 01:17:13 AM
how about change the trading unit to MB ?
GB is too big..
GB is too big..
Indeed, is more room for price increase if is traded in MB.
Agree, I don't see the point in trading GBytes when we can trade MBytes.
April 14, 2017, 01:14:44 AM
Getting byteball on bittrex is really awesome and a huge move forward. If only we could get an exchange for blackbytes, either into byteball or bitcoin so I can get more byteball, I would be happy. The trading on slack is okay, but actually making the deals is much harder and inconvenient than it would be on an exchange.
April 14, 2017, 12:42:53 AM
how about change the trading unit to MB ?
GB is too big..
GB is too big..
Indeed, is more room for price increase if is traded in MB.
April 13, 2017, 11:39:12 PM
we should updates the coinmarketcap data.
it's not that accurate.
I already sent required info about new avl. supply & new exchange bittrex. It takes a bit longer to update... it's not that accurate.
April 13, 2017, 11:32:45 PM
Its funny when you check coinmarketcap and see all these bs pump and dump coins or ripoff coins which are just variations of pos/pow shit. Byteball which is something completely new (DAG) has potential to truly hit a billion market cap someday. I really believe that.
April 13, 2017, 10:47:04 PM
we should updates the coinmarketcap data.
it's not that accurate.
it's not that accurate.
April 13, 2017, 10:38:40 PM
for me wallet works good, no problems on windows 7 and 10
we got bittrex now, finally serious exchange
we got bittrex now, finally serious exchange
April 13, 2017, 09:27:45 PM
@tonych, the same problem with version 1.7.1, any help here?
I am trying to sync my byteball wallet from a couple of weeks ago and it gets about a third of the way (35-45%) and then stops making progress. When I close and reopen the wallet, I get this error and the program closes:
Uncaught exception: Error: known bad go38q4DxyfamiSTzl5rmEBooilX0qGmoS36Wc9zVEY=: authentifier verification failed
Any ideas what to do? I have several full backups of the byteball folder, but for every one of them I run into exactly the same problem.
Uncaught exception: Error: known bad go38q4DxyfamiSTzl5rmEBooilX0qGmoS36Wc9zVEY=: authentifier verification failed
Any ideas what to do? I have several full backups of the byteball folder, but for every one of them I run into exactly the same problem.
+1 got same error
Uncaught exception: Error: known bad
go38q+DxyfamiSTzl5rmEBooilX0qGmoS36Wc9zVEY=
authentifier verification failed
Interesting. I got a similar error with 1.7.1, almost immediately after startup. I didn't record the actual string though. I switched to a backup and the error did not reappear yet, but synch is very slow as is often the case - 70% now, about 5 hours in.
Edit: Update - I left the 1.7.1 wallet running from the backup file overnight. After about 8 hours it had reached 80% synched, but it seemed stalled at that number after a few more hours. I closed it and restarted, which in the past has always fixed these apparent stalls in synching.
On restart it quickly threw the error above, with the same "known bad" string as other posters got, so it seems there are at least three of us with this problem, using the latest version (1.7.1).
April 13, 2017, 08:52:08 PM
how about change the trading unit to MB ?
GB is too big..
GB is too big..
Jump to: