Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to support Feathercoin? #80

Closed
cqtenq opened this issue Apr 13, 2015 · 2 comments
Closed

How to support Feathercoin? #80

cqtenq opened this issue Apr 13, 2015 · 2 comments
Labels
question Inquiry inviting a reply. Point of controversy.

Comments

@cqtenq
Copy link

cqtenq commented Apr 13, 2015

Feathercoin Core 0.9.3 wallet have support OP_RETURN , I think FTC and BTC are the same. How to support Feathercoin?
I change RPC port 8332 to 9337, blockstore start OK and blockstore-cli Error.

blockstore-cli preorder swiftonsecurity N876Ywf8bL5JWMPbHvjHP2AaSF1Ap8Wg4qAn9AAiQbmYFWPh2vqe
{
"error": "UnboundLocalError: local variable 'secret_exponent' referenced before assignment",
"traceback": [
"Traceback (most recent call last):",
" File "/usr/local/lib/python2.7/dist-packages/blockstore/blockstored.py", line 253, in jsonrpc_preorder",
" blockchain_client=blockchain_client, testset=True)",
" File "/usr/local/lib/python2.7/dist-packages/blockstore/lib/operations/preorder.py", line 28, in broadcast",
" hash160 = BitcoinPrivateKey(private_key).public_key().hash160()",
" File "/usr/local/lib/python2.7/dist-packages/coinkit/privatekey.py", line 61, in init",
" if not is_secret_exponent(secret_exponent, self._curve.order):",
"UnboundLocalError: local variable 'secret_exponent' referenced before assignment"
]
}

@muneeb-ali
Copy link
Member

You're right that given that FTC has support for OP_RETURN, it's possible to support Blockstore on top of FTC. However, keep in mind that the "virtual blockchain" (see this) on FTC will not be the same as the "virtual blockchain" on BTC (unless everyone is broadcasting the exact same name_ops on the FTC blockchain as well). You can think of this as creating a parallel universe (or a parallel chat channel) that no one is really using because we expect most people to use the BTC blockchain for now.

Are you trying to create new namespace(s) on top of FTC using Blockstore?

On a separate note, it's probably a good idea to start embedding the Merkle tree root hash of the blockstore namespace in other alt-coin blockchains periodically, but this is different from broadcasting all name_ops on an alt-coin.

@muneeb-ali muneeb-ali added the question Inquiry inviting a reply. Point of controversy. label May 18, 2015
@jcnelson
Copy link
Member

Hi @cqtenq,

The problem you were encountering was due to a now-fixed bug in pybitcoin, whereby pybitcoin did not properly handle compressed WIF-encoded keys. Creating a private key as follows works for me:

>>> import pybitcoin
>>> pybitcoin.BitcoinPrivateKey("N876Ywf8bL5JWMPbHvjHP2AaSF1Ap8Wg4qAn9AAiQbmYFWPh2vqe")
<pybitcoin.privatekey.BitcoinPrivateKey instance at 0x7fc3e8f5de60>
>>> 

I'm closing this issue for lack of activity. Please re-open if you encounter this problem again.

-Jude

muneeb-ali added a commit that referenced this issue Aug 1, 2016
updated for changes in blockstore RPC call
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Inquiry inviting a reply. Point of controversy.
Projects
None yet
Development

No branches or pull requests

3 participants