Show Posts
|
Pages: [1] 2 »
|
All mails from liqui go into my spam folder, so check your spam folder
|
|
|
Whenever I try to make a request through the API, I get a 404 response. I think the error may be caused by how I'm passing in the "method" parameter. The docs don't really explain clearly how this is done...
Has anyone been able to get the trade API to work? Also, why is there no "get deposit address" endpoint? Is this planned for the future?
|
|
|
http://insight.leo2moon.com/ seems to be down. Is this service still maintained? I want to add LEOcoin to my software project, but I need a working API service in order to add it.
|
|
|
I'm having a problem with the bitcore-lib fork found at: https://github.com/Groestlcoin/bitcore-libWhen I try to run "gulp test" I get the following error: Error: Cannot find module 'groestl-hash-js'I'd make an issue on github but for some reason that repo doesn't allow you to make an issue... It looks like the dependency wasn't added to the project correctly. Thats odd that you are not able to make an issue on github. I think i know what is the issue, can you tell me what you are trying to achieve? For example, are you trying to setup groestlsight or groestlpay? Or do you need the bitcore-lib fork for another project like moneywagon? I'm adding GRS to a fork of bitcore I'm trying to get started called altcore: https://github.com/priestc/altcore-libI think i figured out the problem: There is a file called "npm-shrinkwrap.json" which lists all the dependencies but not groestl-hash-js, so it doesn't install that dependency. If you delete the file it'll work, or run "npm shrinkwrap" to update the file.
|
|
|
I'm having a problem with the bitcore-lib fork found at: https://github.com/Groestlcoin/bitcore-libWhen I try to run "gulp test" I get the following error: Error: Cannot find module 'groestl-hash-js'I'd make an issue on github but for some reason that repo doesn't allow you to make an issue... It looks like the dependency wasn't added to the project correctly.
|
|
|
Has anyone tried to get any other exchanges to list the coin for trading? I suggest maybe Cryptopia or NovaExchange. Those exchanges seem to have a lot of coins listed, many far more obscure than RIC. I've used Cryptopia a bit and it seems fine, and have used Nova a bit less but it seemed to work well too. It seems Poloniex are never going to fix their RIC wallet, so I've sold my RIC on there and am waitingto jump back in when there exist a new exchange.
|
|
|
Can someone explain how this "hacking" of the chain occurred? I've never heard of such a thing happening to another cryptocurrency, so I'm curious how it went down.
|
|
|
Can the devs get a block explorer running? I suggest Bitpay Insight, as it's the best block explorer software out there.
|
|
|
I am confused, the paper wallet generator here: http://vergecurrency.com/paper-wallet/index.html produces addresses that start with 1, but all verge block explorers use addresses that start with D. I assume th block explorer are correct... i there a correct paper wallet generator in existence?
|
|
|
Is there a TSE paper wallet generator? I can add TSE to my paper wallet generator at multiexplorer.com but I need to know the WIF byte. Normally you can get the WIF byte from looking at chainprams.cpp in the github repo, but for some reason tattoocoin doesn't have a chainparams.cpp...I figured it out. You can now make paper wallets for tse at https://multiexplorer.com/paper_wallet
|
|
|
It look like the block explorer at http://blockchain.beavercoin.org/ is not working. Could someone please get that going? If so, I can add BVC to my webwallet project multiexplorer, but only if there is a working insight instance available... (cryptoid doesn't have the functionlity that Insight has)
|
|
|
If someone wants to pay for the amazon ec2 instance, I can volunteer my services to build a birdcoin block explorer, and also I can add birdcoin to a webwallet that I created (at multiexplorer.com). The web wallet can oly exist if there is a working blockexplorer, which I don't think there is one working at the moment... EC2 instances cost like $15 /month.
|
|
|
You cant send accidentally grs to another coin and vice versa. No more mistakes
That what the version byte is for. The first letter of the address is what keeps you from sending currency to the wrong type of address. All changing the base58 does is make it more error prone. If I had not happened to stumble upon the fact that GRS uses a different hash algorithm for addresses, I may have implemented GRS to some application using sha256, which would have resulted in me and anyone using that app to lose money by sending to an invalid address. Is very unusual for an altcoin to change the address hash, in fact GRS is the first I've come upon. I see the bip32utils project you have forked already includes a base58 implementation using groestl. Could you put it up on pypi so I can add it to my project? My project is called moneywagon, it's a cryptocurrency platform for building wallets and exchanges and stuff like that on top of. Also, it seems you also removed sha256 from the transaction serialization code too? If so then another forked python library with groetsl support is needed to make transactions, so the groestl-hash function needs to be added to pypi too. Also I noticed there is a groestl fork of bitpay insight on the groestlcoin github. Is there a pubic instance of this running?
|
|
|
So yes, base58 address encoding uses double groestl512 instead of double sha256.
I see. If there a reason for this? I can understand why you'd change the POW, but why change the address hash? There doesn't seem to be any benefit to doing that, other than to make it harder for people like me to implement wallets. I now have to fork every base58 library to replace sha256 with groestl512, which I've done here: https://github.com/priestc/Groestlbase58, except i can't find a good Groestl implementation in python, so Groestlcoin will unfortunately remain unimplemented in my project ![Sad](https://bitcointalk.org/Smileys/default/sad.gif)
|
|
|
I tried to generate an address with the Groestlcoin paper wallet generator, but the address it gave had a "checksum error". The rivate key also gives me a checksum error too.
Here is the address: Foi3FNkp6f2u1aVyBLpUuQjAtvXvLoQyDz
and the corresponding private key also gives me a checksum error: 5KDcgddMkhPsLFypd1giap5fziz43SazRupaTmLYWvVmcu5YS9g
by any chance did Groestlcoin change the base58 address encoding that bitcoin uses? Why would it give me this error?
Here is the python code I'm using:
>>> from base58 import b58decode_check >>> b58decode_check("Foi3FNkp6f2u1aVyBLpUuQjAtvXvLoQyDz") ValueError: Invalid checksum >>> b58decode_check("5KDcgddMkhPsLFypd1giap5fziz43SazRupaTmLYWvVmcu5YS9g") ValueError: Invalid checksum
This base58 library works fine for other BTC forked coins like LTC, PPC, Doge, etc...
|
|
|
|