|
interested in buying 100,000 - 200,000 - let me know if you want to sell
|
|
|
|
Cedric, any news man?? Can you please give us an update on things? I truly appreciate it!!
Yes, it's coming, just need to be patient for a bit longer..  |
|
|
|
Thanks very much. Looks great but cannot get it working unfortunately. I have /usr/include/openssl/bn.h but am getting the following error: undefined symbol: BN_init Looking in bn.h 'BN_init' does not seem to exist... Will keep trying though. |
|
|
|
I do have some Perl but in the bit privkey → pubkey I cheat via "use Inline" . C compiler and libssl-dev required. Interested..  |
|
|
|
Does any one have a minimal / basic perl script that can generate a public addresses given a 32 byte private key? Most of the perl code examples on Github are unmaintained / broken / years old and I am having troubles getting any of them working. Something similar to this python code: import ecdsa
secp256k1curve=ecdsa.ellipticcurve.CurveFp(115792089237316195423570985008687907853269984665640564039457584007908834671663,0,7)
secp256k1point=ecdsa.ellipticcurve.Point(secp256k1curve,0x79BE667EF9DCBBAC55A06295CE870B07029BFCDB2DCE28D959F2815B16F81798,0x483ADA7726A3C4655DA4FBFC0E1108A8FD17B448A68554199C47D08FFB10D4B8,0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364141)
secp256k1=ecdsa.curves.Curve('secp256k1',secp256k1curve,secp256k1point,(1,3,132,0,10))
#--------------------------------------
import binascii, hashlib
def addy(pk):
pko=ecdsa.SigningKey.from_secret_exponent(pk,secp256k1)
pubkey=binascii.hexlify(pko.get_verifying_key().to_string())
pubkey2=hashlib.sha256(binascii.unhexlify('04'+pubkey)).hexdigest()
pubkey3=hashlib.new('ripemd160',binascii.unhexlify(pubkey2)).hexdigest()
pubkey4=hashlib.sha256(binascii.unhexlify('00'+pubkey3)).hexdigest()
pubkey5=hashlib.sha256(binascii.unhexlify(pubkey4)).hexdigest()
pubkey6=pubkey3+pubkey5[:8]
pubnum=int(pubkey6,16)
pubnumlist=[]
while pubnum!=0: pubnumlist.append(pubnum%58); pubnum/=58
address=''
for l in ['123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz'[x] for x in pubnumlist]:
address=l+address
return '1'+address
print addy(0x18E14A7B6A307F426A94F8114701E7C8E774E7F9A47E2C2035DB29A206321725)
print addy(int(hashlib.sha256('something small and easy to remember but not easy to guess').hexdigest(),16)) ref: https://bitcointalk.org/index.php?topic=84238.0Would be happy to provide a small bounty. thanks |
|
|
|
 You can now send tips through Twitter with your CoinWallet.co account. Simply use a current CoinWallet.co account or start a new one (takes about 30 seconds). Fund your Bitcoindark wallet. Connect your CoinWallet.co account to your Twitter account (from the dashboard on CoinWallet.co) Send tips on Twitter by tweeting something like the following: @coinwalletco tip @someuser $BTCD 1 For more information please visit: https://www.coinwallet.co/twitter/tip/howto |
|
|
|
You can now send tips through Twitter with your CoinWallet.co account. Simply use a current CoinWallet.co account or start a new one (takes about 30 seconds). Fund your UNO wallet. Connect your CoinWallet.co account to your Twitter account (from the dashboard on CoinWallet.co) Send tips on Twitter by tweeting something like the following: @coinwalletco tip @someuser $UNO 0.5 For more information please visit: https://www.coinwallet.co/twitter/tip/howto |
|
|
|
Yeah, seems like people are right on the verge of realising the potential of this coin. But sadly most people here seem to be more interested in 'AnaLCoin' and similar shite and will probably just call me a hyper / scammer / pump and dumper  In a few months time don't say we didn't warn you.  |
|
|
|
Are they equal partners in this, or is Markus just working for hire for Fyrstikken? not that it matters - as long as the development goes on ... but i would think when the devs come out and let us know whats happening - maybe we will know what to expect as well ... time - thats all ... they are probably busy with work and their own lives at the moment ... ... #crysx After taking BTC from investors the least they could do is drop in to the thread now and then and let us know what is going on. |
|
|
|
Centralized and regulated coin Retro site design "World Group" with a gmail address as contact MLM style network Promises guaranteed profit Must be legit... In exchange for your vids here's an other one : https://www.youtube.com/watch?v=cIasr2AiyZ0You summed it up well.  |
|
|
|
Is it worthwhile to Join the slack group?
Yes, but you need to be an ICO investor. There is talk of creating a public slack group or moving discussions more towards IRC. Thank you I am an ICO investor, so I will be putting in my ticket with my signed ICO address shortly. See you in the slack! Look forward to seeing you there Article on startupdope.com mentioned XAI "..One of those alternative cryptocurrencies, XAI (Sapience AIFX), has gone beyond being a simple alternative to bitcoin and actively been developing a solution that can be used on.." read full article here: http://startupdope.com/bitcoinbackbonesecuretelecom/Wow, that is a great mention!! |
|
|
|
Is it worthwhile to Join the slack group?
Yes, but you need to be an ICO investor. There is talk of creating a public slack group or moving discussions more towards IRC. |
|
|
|
Talking about the 15-30'is seconds delay right after starting the daemon? If so, its been always like this, at least for me, on puny little VPS's. After that, its pretty snappy
No, 30+ second delay all the time.
edit: I have thousands of 'dust' inputs - I wonder if that has anything to do with it. Although other wallets I host often have far more dust inputs and still have normal response times.
I did feel a slow down a few versions back, on a particularly large volume wallet I had. Other wallets were quicker. But these were QT on a Mac laptop. But a version or two later no more lag on that wallet. If its dust, can't you consolidate them into one input and get rid of them? Yes, running my dust sweeper now. The upgraded wallet seems to have fixed the problem of getting stuck on blocks every 10 minutes or so, strangely - which was making my duster work very slowly. |
|
|
|
Anyone else notice strange behaviour with the latest Darkcoin client daemon.
On one service I run the response time for 'darkcoind getinfo', for example, is around 30 - 35 seconds (dedicated server with 32GB ram).
All other coins on the same server have response times of sub 1 second.
Also the client regularly seems to get stuck on blocks behind the main chain. For example the client is now stuck on 235905 where as the main explorer is showing the current block as 235924.
"version" : 110125,
"protocolversion" : 70066,
"walletversion" : 60000,
- pls upgrade to walletversion 61000 with Commandline option -upgradewallet (make a backup first !) - pls check in your debug.log for any of these errors ''ERROR: ReadBlockFromDisk :'' if you find such error then delete everything except your wallet.dat and darkcoin.conf to rebuild your blockchain. Thank you for your suggestion. I updated the walletversion using -upgradewallet I checked the last 100000 lines of debug.log for 'ReadBlockFromDisk' and did not find one occurrence so did not delete everything. The problems persist.  "version" : 110125, "protocolversion" : 70066, "walletversion" : 61000, Talking about the 15-30'is seconds delay right after starting the daemon? If so, its been always like this, at least for me, on puny little VPS's. After that, its pretty snappy No, 30+ second delay all the time. edit: I have thousands of 'dust' inputs - I wonder if that has anything to do with it. Although other wallets I host often have far more dust inputs and still have normal response times. |
|
|
|
Anyone else notice strange behaviour with the latest Darkcoin client daemon.
On one service I run the response time for 'darkcoind getinfo', for example, is around 30 - 35 seconds (dedicated server with 32GB ram).
All other coins on the same server have response times of sub 1 second.
Also the client regularly seems to get stuck on blocks behind the main chain. For example the client is now stuck on 235905 where as the main explorer is showing the current block as 235924.
"version" : 110125,
"protocolversion" : 70066,
"walletversion" : 60000,
- pls upgrade to walletversion 61000 with Commandline option -upgradewallet (make a backup first !) - pls check in your debug.log for any of these errors ''ERROR: ReadBlockFromDisk :'' if you find such error then delete everything except your wallet.dat and darkcoin.conf to rebuild your blockchain. Thank you for your suggestion. I updated the walletversion using -upgradewallet I checked the last 100000 lines of debug.log for 'ReadBlockFromDisk' and did not find one occurrence so did not delete everything. The problems persist. "version" : 110125, "protocolversion" : 70066, "walletversion" : 61000, |
|
|
|
|
Anyone else notice strange behaviour with the latest Darkcoin client daemon.
On one service I run the response time for 'darkcoind getinfo', for example, is around 30 - 35 seconds (dedicated server with 32GB ram).
All other coins on the same server have response times of sub 1 second.
Also the client regularly seems to get stuck on blocks behind the main chain. For example the client is now stuck on 235905 where as the main explorer is showing the current block as 235924.
"version" : 110125,
"protocolversion" : 70066,
"walletversion" : 60000,
|
|
|
|
I can't really speak for the price talk, alt markets are crazy these days with low volume and uncertainty around BTC, although I think we will see a positive outcome from this latest US Marshals auction and the BTC 3d chart is looking pretty good to me. What I can say is that I have a pretty big vision for this platform that hits hard both on the tech end and on the adoption/user experience end, and I want to push things harder/farther than most other coins have managed to do so far in terms of achieving a certain level of ease-of-use and intuitiveness that makes the onramp easier for kind of the next layer out in the onion of more general tech enthusiasts. I am not a Bitcoin maximalist, but I do believe in Bitcoin and the bitcoin protocol, and so another agenda for me is looking at opportunities for technology crossover to Bitcoin and how we can maybe achieve some direct integration scenarios. All of that will make more sense as our infographics and mar-com materials start to come out. Here's a peak at the roadmap just for the AI Core through the end of 4Q2015:  http://issuu.com/sapienceaifx/docs/_internal__-_sapience_aifx_2015_ai_Don't mind me, I just watched Citizen Four last week and had the "holy shit" reaction, so there you go I can leak my own Top Secret document  Note that neuromining is NOT something like AI POW algorithms or anything like that, its something different. What we are doing is getting the basic "scale out" working first, and then this will enable "scale up" at the edges and another new type of micro-economy/market aka the Neural Cloud. are you guy's ready for next week release? As i understood AI Core phase 1 going live next week, this is HUGE step forward. Yes, looking forward to it.. |
|
|
|
Maybe bittrex staking all the coins on their exchange? (jk) I have often wondered if they do that. |
|
|
|
|
Show Posts
