Answers to this question are constantly posted on this forum and on Reddit by people who are not software engineers/developers, nor product managers. Either that or they are truly terrible at their jobs. Reddit in particular has really turned into a garbage dump, but that's something for another discussion. Anyway, in a business context you want to build software that meets your customer's expectations, so understanding how a user makes use of your software solution is really important for smooth communication and shared understanding between management, marketing and engineering. Normally you want to write out really detailed user stories/journeys, maybe even draw diagrams or create mock-ups that demonstrate the exact problem you're trying to solve and how your thing will solve it. Here's a teaser: Alice is at a farmer's market and wants to buy broccoli from a vendor. How does she pay? Here are just a few important details that we need to know first:
- What country is Alice in, and what are the economic conditions?
- How much money does she make every year/how well off is she?
- How technologically sophisticated is she/how old is she?
- What tastes and preferences does Alice have/what prejudices her in certain ways?
We need a lot more information before we start talking about what BIP we can code up in a day. If you think about these questions only from your own perspective and experience, you're discounting the majority of people on this planet that want to use the same technology. Bitcoin's value depends mainly on how many people can safely use it, and if it's not in use by the largest number of people possible, it will not achieve it's full potential/value. The correct answer to the question in this poll is "it depends". Bitcoin is for humans, and humans have different needs. Most likely every redditor and bitcoin.org poster's favorite potential use case, "in-person payments at high volume merchants", will not be satisfied by Bitcoin directly. Use something else for that one narrow use case if Bitcoin isn't doing it for you, and support the engineers who are working to make Bitcoin more secure and stable, goddamnit  |
|
|
|
One thing I have thought about is that with bitcoin, someone could force you to hand over your private key. What sort of safeguards are there to prevent this happening, or to prevent them taking everything in that wallet?
One thing one can do is leave Bitcoins on an exchange that will only allow you to withdraw $1000 worth per day, but then you run the risk of the exchange being hacked....what are the other options?
Trezor blog has a step by step guide for just this scenario: https://blog.trezor.io/hide-your-trezor-wallets-with-multiple-passphrases-f2e0834026eb |
|
|
|
I'm starting to notice the beginnings of Facebook censoring content that they do not agree with. While I know this has been going on for a while in niche ways, I have started seeing it myself now.
I would love to switch over to Taringa and actually get paid in bitcoins for posting but their site is all in Spanish and I could not locate an English version.
Are there any Facebook alternatives out there that will most likely take over as Facebook becomes more and more SJWish?
I don't really like Facebook in the first place but where I work they block most websites and I can waste my time on there and have simple communication with all of my family on there.
It seems you have to have a Facebook account in order to use Taringa, that's probably their KYC mechanism that they use when paying their top producing content creators. It would be great if such a thing were created in a pure p2p format; maybe Open Bazaar will eventually add similar features and become a web browser alternative. |
|
|
|
unless you're going to put more than $2,500 on the card.
So does this mean that you can only spend $2500 total before doing more complex KYC, or does it mean you can load and spend $2499 every month on the card in perpetuity? |
|
|
|
I've been reading this thread with a lot of interest. Unfortunately I'm still a newbie (and English is not my native language) and I'm not sure I understand everything that is said. I thought it would be best to explain my situation to find out what to do... I've got a 3 BTC on my external Trezor device I've got a bit more than 1 on Coinbase and a small amount of 'spending money' on Blockchain.info So if I'm right it's best to move out of Coinbase. But should I move my Trezor BTC too? How reliable is their 'backup' plan? And where to move? I don't want everything stored in one place. After reading this thread, my first reaction is to move everything to an Electrum wallet or Multibit, but I'm not really fond of desktop wallets - I don't really know how vulnerable my laptop is. How about exchanging part of the BTC into another cryptocurrency? I'm pretty confused here...  Here's what I have gathered to be the easiest and safest way to claim your new coins after the fork: - Send the coins your have in your blockchain.info wallet and on your Coinbase account to your Trezor for safe storage
- Send the coins that are on your Trezor to an exchange that lists both BCC and BCU (dinofelis used Kraken)
- You will be able to sell the coins you don't want on the exchange
- Withdraw the coins from the exchange and send the coins to your Trezor
The other option is to do nothing, Bitcoin will continue to work as normal. |
|
|
|
Looking forward to trying this out! |
|
|
|
If you're running any network threat protection services from anti-malware or anti-virus packages, it might be blocking the traffic. It could also be something in the code that leaves the port session open without properly closing the session, so you can't start a new rpc session. Try using wireshark on one of your endpoints and see if the channel is being closed correctly. If you're not already doing so, whitelist your src/dest ip addresses in your firewall(s).
I just realized the issue: I completely forgot I was running TOR browser. I don't have time to play with TOR browser settings right now, so just closing it out resolves the issue. |
|
|
|
Most probably, the safest method is to use an exchange that lists both coins, and has provisions to do the split for you, that is, to send the "unified old coins" to an address attached to you on the exchange. The exchange will then give you IOU of both types of coins. You can trade those (for instance, selling off your bitcoinx and buy more bitcoin, or selling off bitcoin to get more bitcoinx). When you will withdraw the coins, they will be 1 type only.
But be sure you use an exchange that knows how to handle this. Most big exchanges learned this during the ETH/ETC split. Some made big mistakes. Some stole the ETC of their customers, pretending they didn't "list" ETC.
I agree that outsourcing the problem is *perhaps* the safest way to proceed. Which exchanges have a proven track record of doing this for ETC that you could recommend? |
|
|
|
Get yourself some dust from a block mined on one of the chains.
Do you think it would be better to use fiat to buy a small amount on an exchange, or is it better to have a miner running that can mine some dust in a more reliable and timely manner? If so, which miner would you recommend (e.g. 21co)? Combine that dust with your existing coins by sending a transaction to another address that you control. Since those coin base rewards don't exist on the other chain, this transaction will only be valid on one chain.
Let's imagine I have a cold wallet with a stash of 3 XBT. I assume I can import these private keys into *both* BU and Core wallets at the same time. On each client, I should see a balance of 3 XBT. Now I start to work with the BU CLI: I need to craft a raw transaction with 2 or more inputs, and 2 or more outputs that go back to my own BU wallet. Is that right? After that, send your coins on the other chain to a new address that you control (extra measure just to be sure). At this point, your coins will be effectively disassociated between the two existing chains.
So now I open up my Core wallet, get a new receiving address, and then use my BU wallet to send my entire BU balance to my Core wallet. After no less than 1 confirmation, I see my Core balance is now 6 XBT, and my BU wallet is 0 XBT. Correct? |
|
|
|
Did you try to increase the rpc threads, i.e. something like: in your .conf file ? HTH I'm going to try it, thanks! Restarted the server, so now I have to wait for it to verify the last 288 blocks... |
|
|
|
If I have my coins in cold storage, what's the procedure if I want to sell off my Unlimited coins? I assume it's the following: - Export my private keys from my cold wallet (or wherever they are stored)
- Download and install Bitcoin Unlimited client
- Import my private keys into my Bitcoin Unlimited client
- Send my BU coins to an exchange (say shapeshift.io) in exchange for Core coins or fiat or whatever
- Provide new cold storage addresses to receive the new Core coins
Is that right? No. Your BU transaction can be replayed on the Core chain, with the result that you lose all your Core coins. Ok. What's the best way to accomplish it then? |
|
|
|
Also, "success" looks like this I think: 2017-03-14 06:45:06 connect() to [2002:6dc4:bb6e::6dc4:bb6e]:8333 failed: No route to host (65)
2017-03-14 06:47:08 keypool added key 544, size=101
2017-03-14 06:47:08 keypool reserve 444
2017-03-14 06:47:08 keypool keep 444
2017-03-14 06:47:09 keypool added key 545, size=101
2017-03-14 06:47:09 keypool reserve 445
2017-03-14 06:47:10 keypool keep 445
|
|
|
|
I wrote up a script that uses this repo: https://github.com/laanwj/bitcoin-pythonI know it's an older repo but I like it. Anyway, it works great most of the time. But sometimes my script just can't connect to my bitcoind -server for some inexplicable reason. Does anyone have a guess as to what that reason might be? I just upgraded to the latest version of core but the seemingly random issue persists. class BitcoinConnection(object):
"""
A BitcoinConnection object defines a connection to a bitcoin server.
It is a thin wrapper around a JSON-RPC API connection.
Arguments to constructor:
- *user* -- Authenticate as user.
- *password* -- Authentication password.
- *host* -- Bitcoin JSON-RPC host.
- *port* -- Bitcoin JSON-RPC port.
"""
def __init__(self, user, password, host='localhost', port=8332,
use_https=False):
"""
Create a new bitcoin server connection.
"""
url = 'http{s}://{user}:{password}@{host}:{port}/'.format(
s='s' if use_https else '',
user=user, password=password, host=host, port=port)
self.url = url
self.proxy = AuthServiceProxy(url, exception_wrapper=wrap_exception)
And I am using this method: def getrawchangeaddress(self, account=None):
"""
Returns a new bitcoin raw change address for properly handling change.
"""
return self.proxy.getrawchangeaddress()
Bitcoind shows this in the log: 2017-03-14 08:33:36 connect() to 71.239.98.166:8333 failed after select(): Connection refused (61)
|
|
|
|
Writing/updating in progress!
You will be able then to decide to sell a little on one side, or the other, or keep them still and wait longer term.
Good post, thanks for the translation. Let's say a fork occurs, and it's Bitcoin Unlimited branching off of Core. If I have my coins in cold storage, what's the procedure if I want to sell off my Unlimited coins? I assume it's the following: - Export my private keys from my cold wallet (or wherever they are stored)
- Download and install Bitcoin Unlimited client
- Import my private keys into my Bitcoin Unlimited client
- Send my BU coins to an exchange (say shapeshift.io) in exchange for Core coins or fiat or whatever
- Provide new cold storage addresses to receive the new Core coins
Is that right? |
|
|
|
I just wrote some code yesterday that uses getrawtransaction, so I'll need to make some changes  |
|
|
|
The error is always thrown with bitcoin-cli signrawtransaction
Interesting. Try using your original signrawtransaction command but with "vout":0 instead of "vout":1Success! I finally got signrawtransaction to sign the raw transaction, thank you! Here's my code to create the raw transaction: bitcoin-cli createrawtransaction '[{"txid":"0d53507afc671e57841e3f72cee5db1324da4fa0c42a50c98872b820d2a2c768","vout":0,"scriptPubKey":"76a9141e460f008264743caa92c9d23f944216fd29c7a788ac"}]' '{"1EhPUwR9BkWWJ1K9rWjxSFbBMGKXKozCim":0.0003,"18PgTTpQP9snFrJfZk8KCHKEXP9uUX7jLW":0.00008}'
It outputs the hash, and I copy and paste that hash into the signrawtransaction command. Now signing: 687_2$ bitcoin-cli signrawtransaction '010000000168c7a2d220b87288c9502ac4a04fda2413dbe5ce723f1e84571e67fc7a50530d0000000000ffffffff0230750000000000001976a914963d0a59d3b0ccfd0df3c95c972bee98e06ba19688ac401f0000000000001976a9145112f7d2f5818bc8c1921e3181f2d27822feafb388ac00000000' '[{"txid":"0d53507afc671e57841e3f72cee5db1324da4fa0c42a50c98872b820d2a2c768","vout":0,"scriptPubKey":"76a9141e460f008264743caa92c9d23f944216fd29c7a788ac"}]' '["myprivatekey"]'
Output: {
"hex": "010000000168c7a2d220b87288c9502ac4a04fda2413dbe5ce723f1e84571e67fc7a50530d000000006b483045022100be8112238a16d24ccc1769f98d5df7ec508f99eaf6b97ec42dcece8b9360328402207c07a830266c34aa77d1612e04d90757f8149d4df4785ada8cf957334497878b01210285019768580fb3d7d37928993b17e951527e5c2c2084a78013248e8fe572acecffffffff0230750000000000001976a914963d0a59d3b0ccfd0df3c95c972bee98e06ba19688ac401f0000000000001976a9145112f7d2f5818bc8c1921e3181f2d27822feafb388ac00000000",
"complete": true
}
|
|
|
|
The error is always thrown with bitcoin-cli signrawtransaction createrawtransaction always generates a nice hash: 010000000168c7a2d220b87288c9502ac4a04fda2413dbe5ce723f1e84571e67fc7a50530d0100000000ffffffff0230750000000000001976a914963d0a59d3b0ccfd0df3c95c972bee98e06ba19688ac401f0000000000001976a9145112f7d2f5818bc8c1921e3181f2d27822feafb388ac00000000
|
|
|
|
Thanks guys, but now I have this problem: error code: -3
error message:
Missing scriptPubKey
error code: -8
error message:
Invalid parameter, missing vout key
|
|
|
|
Hi all, I'm trying to create a raw transaction using bitcoin-cli. First I look at the transaction: 687_2$ bitcoin-cli listunspent
[
{
"txid": "0d53507afc671e57841e3f72cee5db1324da4fa0c42a50c98872b820d2a2c768",
"vout": 0,
"address": "13m5CWgygXuCbwuMo6MFtqNsiZT8uY1o6Q",
"account": "",
"scriptPubKey": "76a9141e460f008264743caa92c9d23f944216fd29c7a788ac",
"amount": 0.00039000,
"confirmations": 21,
"spendable": true,
"solvable": true
}
]
Then I create the raw transaction: bitcoin-cli createrawtransaction '[{"txid":"0d53507afc671e57841e3f72cee5db1324da4fa0c42a50c98872b820d2a2c768","vout":1,"scriptPubKey":"76a9141e460f008264743caa92c9d23f944216fd29c7a788ac"}]' '{"1EhPUwR9BkWWJ1K9rWjxSFbBMGKXKozCim":0.00038,"15sGXSMk99DUzwPMXqCevYB1gmS3c62CQr":0.00007}'
This gives me the hex: 010000000168c7a2d220b87288c9502ac4a04fda2413dbe5ce723f1e84571e67fc7a50530d0100000000ffffffff0270940000000000001976a914963d0a59d3b0ccfd0df3c95c972bee98e06ba19688ac581b0000000000001976a914356242ba76e9e8df980ac9d2d5399dee1233e45488ac00000000
Ok, now I want to sign the transaction. I format the command as prescribed:
687_2$ bitcoin-cli signrawtransaction '010000000168c7a2d220b87288c9502ac4a04fda2413dbe5ce723f1e84571e67fc7a50530d0100000000ffffffff0270940000000000001976a914963d0a59d3b0ccfd0df3c95c972bee98e06ba19688ac581b0000000000001976a914356242ba76e9e8df980ac9d2d5399dee1233e45488ac00000000' '[{"txid":"0d53507afc671e57841e3f72cee5db1324da4fa0c42a50c98872b820d2a2c768","vout":1,"scriptPubKey":"76a9141e460f008264743caa92c9d23f944216fd29c7a788ac"}]'
This results in the error: error code: -22
error message:
Previous output scriptPubKey mismatch:
OP_DUP OP_HASH160 cbe0394e3f79b2f4f4e87191c638df0e8795bf92 OP_EQUALVERIFY OP_CHECKSIG
vs:
OP_DUP OP_HASH160 1e460f008264743caa92c9d23f944216fd29c7a7 OP_EQUALVERIFY OP_CHECKSIG
I've tried a few different ways of breaking this, looked here: https://www.reddit.com/r/Bitcoin/comments/2ebaow/how_to_create_a_raw_transaction_in_bitcoin_qt/ which doesn't seem to help, and I tried Greg's example: https://people.xiph.org/~greg/signdemo.txt as well; that one worked but I couldn't send the raw transaction (insufficient fee, or something. It made sense). This seems like a trivial issue, maybe I've just been looking at my monitor too long. Does anyone see what I'm doing wrong? Is there something I'm missing? |
|
|
|
This is a serious issue and need to come up with a solution soon, I need to pay 65000sat to move 0.21BTC because the first two transactions was stalked for hours and not confirmed.
This is the solution. Bitcoin is currently designed to force users into a "fee war". The idea is that those who really want to use bitcoin will be willing to pay the fee. If bitcoin isn't important enough for a user's needs, then the fee will discourage them so they will go elsewhere. The assumption is that the system will eventually reach an equilibrium where the fees are high enough to keep the transaction volume at nearly always full blocks. It will be interesting to see if that equilibrium actually occurs, or if the whole system collapses as users all flock to some other system. Either way, it's going to be fun to watch this experiment unfold. I can't wait for all these people who are clogging up the forums with clueless and irreverent posts about block sizes and other technical issues (and who are obviously not engineers, not here to learn, and also probably own little to no Bitcoin) to emigrate. |
|
|
|
|
Show Posts
