Bitcoin Forum
May 27, 2024, 07:47:41 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 [4] 5 6 7 »
61  Other / Off-topic / Re: Bitcoin is satanic and Satoshi is lucifer! My uncle claims! on: October 16, 2014, 11:20:43 AM
Makes sense. God is the ultimate authoritarian and Satan was the first antiauthoritarian. If Satan wanted to undermine the authoritarians on Earth, what better way than create Bitcoin? If today's Earthly authorities follow God's example, I expect all us Bitcoiners to be cast into the dark web. But don't worry. It'll be fun in there.

The next paragraph is true.

The first paragraph is false.

62  Bitcoin / Bitcoin Discussion / Re: Bitcoin, btcd and Golang on: October 16, 2014, 06:53:08 AM
I've started looking at btcd and the pdfs here have helped me get started. Thanks for posting them.

Can you post a link about that?

Hi. I'm not sure how to resolve "that" in your question, so here are several links.  Smiley

Here are links about btcd (a reimplementation of the Bitcoin protocol in Go):

https://opensource.conformal.com/wiki/btcd
https://github.com/conformal/btcd

Here are links to the pdfs (linked earlier in the thread). I haven't watched the videos because it's difficult to watch videos while using Tor.

https://github.com/ATXBTC/Presentations

None of this is my work. I'm simply someone learning about it. I'm a functional programmer. I coded a BIP0032/HD Wallet in lisp last year (with limited functionality, and I doubt anyone other than me uses it at all). I was going to post a link to it here, but it seems github may have deleted my account and repository without informing me. So instead I guess I'll say: Don't trust github.
63  Bitcoin / Bitcoin Discussion / Re: Bitcoin, btcd and Golang on: October 15, 2014, 06:33:29 PM
I've started looking at btcd and the pdfs here have helped me get started. Thanks for posting them.
64  Bitcoin / Bitcoin Discussion / Re: My company can no longer take BTC. on: October 04, 2014, 03:33:26 PM
Yes, GoDaddy sucks. Fine. But switching to a different server or host doesn't address an issue in this thread. Odd that it keeps being brought up. Suppose the OP gets a different server/host. Q: What does he do with it so that he starts making sales in BTC? A: Nothing. He spends money on a better server/host and gets nothing in return.

And advertise? Sure. But advertising is very expensive. The OP would need to decide if spending a few thousand dollars on advertising will result in more than a few thousand dollars worth of BTC in sales. It seems unlikely to have this effect if his current BTC sales are zero.

BTC is a niche. Very few people have it and very few of those use it. If you don't believe me, start a BTC accepting business. Tell me how the crickets sound where you live.
65  Bitcoin / Bitcoin Discussion / Re: My company can no longer take BTC. on: October 04, 2014, 11:13:54 AM
DONT RUN A BITCOIND OR ANY WALLET ON A WEB SERVER!!! seriously!!
no wonder so many people are screaming bitcoin hacks.. you lot make it simple for them
NEVER EVER EVER have private keys on a website

I rented a VPS so bitcoind would be running somewhere with nothing else running (e.g., no apache so no website).

If bitcoind could include "watch-only" addresses, then there wouldn't be the danger of private keys being hackable. But you're right. Since the private keys must be in the wallet in order to watch for transactions, the best advice is not to use it for this purpose. In my case, I imported the private keys into the wallet.dat offline and then encrypted it with a high entropy (128 bit) password. Then I uploaded the encrypted wallet.dat to the VPS. I only wanted it for watching. While I think it was relatively secure (and I never had enough mbits to make it a decent target), your advice is best: don't do it. It was more of a test in my case.

and if you cant even make $2.50 a week profit.. (before even thinking of bitcoin) then you have bigger issues than bitcoin

I agree. That's why I gave up what I was doing and decided never to try anything again the rest of my life. Wish me luck!
66  Bitcoin / Bitcoin Discussion / Re: My company can no longer take BTC. on: October 04, 2014, 10:27:43 AM
I sympathize with the OP. It's not the first story I've heard of small/internet businesses accepting bitcoin but getting few, if any, orders.

Accepting bitcoins shouldn't depend on third parties (e.g., coinbase). However, running your own bitcoind isn't as easy as it's made out to be. I rented a VPS for a few months to try it out. It cost me around $10 a month (and in the end it didn't have enough RAM to work effectively).

I doubt many business are making even $10 extra profit a month by accepting bitcoin.

A lightweight application a business could run just to listen for transactions on the Bitcoin network would help IMO.

I want to thank the OP for being a pioneer and trying to accept bitcoin, and thanks for the report that it wasn't worth it. This is useful information.
67  Bitcoin / Bitcoin Discussion / Re: The transaction fee is just ridiculous. on: September 30, 2014, 11:48:19 AM
If you want to pay 0 tx fees (which I don't recommend), I have three words for you:

createrawtransaction
signrawtransaction
sendrawtransaction

The power is in your hands.
68  Bitcoin / Bitcoin Discussion / Re: Someone please tell me this isn't how transactions always work.... on: August 29, 2014, 11:44:17 AM
(or even to the same address)

No. An address when spent must spend it's total value.

No. An output when spent must spend its total value.

Yes. It's transaction outputs that spend their total value, not addresses. For people who use Bitcoin-QT, do a little experiment building a transaction with "createrawtransaction" in the Help>Debug>Console. DIY is the best form of education.
69  Bitcoin / Bitcoin Discussion / Re: Someone please tell me this isn't how transactions always work.... on: August 29, 2014, 10:09:33 AM
In my opinion, it seems it would be better for the wallet to break up larger outputs into multiple smaller outputs so that less total value is locked up in an unconfirmed transaction.

I think this is the best solution. While it would be helpful if a wallet offered to do this, people can do it themselves now. If you have $60 worth of btc at an address in your wallet, then do this: Before going out just send a couple of $20 transactions to two new addresses (or even to the same address) in your wallet. After that you should have 3 unspent txouts worth about $20. Then there's no need to make change. It's not so different from making sure you don't leave the house with only a $100 bill in your wallet.
70  Bitcoin / Bitcoin Discussion / Re: Bitcoin 51% attack considered harmless on: August 29, 2014, 09:51:33 AM
Having a majority hashpower means you get to decide how future blocks are constructed. If you have more hash power than the rest of the network, you will always persevere in a race to construct a longer blockchain. If I have and maintain a 50.1%+ hash rate and start mining blocks now, ignore blocks mined by others, and do something detrimental like ignore all pending transactions, eventually if not immediately I will have a longer blockchain that will replace the community chain. The certainty that I win becomes higher the more time passes.

What's even more fun is if I withhold my longer empty chain until later. If I have been mining a month silently and am ahead of the network, I can announce my blockchain and wipe a month's mining and transactions. I mine all the bitcoins, but even better, I can get back all the bitcoins I previously owned but spent during that month. This would be a bitcoin killer, 99% of clients immediately wipe the orphan chain data, and it would be a challenge to construct a client ignoring the new chain and get it out to every user before Bitcoin is declared dead.

Think of companies such as merchants and payment processors that have no way of reclaiming their payments if the sender does not retransmit after such a mass block-replace. Such a massive orphanarium will likely break the majority of Bitcoin accounting software running behind sites, maybe even in a history-wiping way depending on how the backend was programmed. The current hashrate is massive, it would take the NSA's million-square-foot Utah facility being converted into all-ASIC miners to have a chance. However, all we need is for a nation state or three-letter-agency to seize the operations of some of the biggest miners to reduce their impact or turn them against us.

This is the real danger of a 51% attack. I hope people read your post and think about it. I've heard people minimize a 51% attack as "someone can double spend for 10 minutes," but it can be much worse than that.
71  Bitcoin / Bitcoin Discussion / Re: I just had a great idea - print bitcoin denominations on: August 29, 2014, 09:35:35 AM
Then you could just print off several of these whenever you need to, and spend them at Bitcoin accepting institutions. JUST LIKE FIAT PAPER MONEY.

The seal on Paperwallets, so far as I have seen, was always a FAIL (just with varying afford to break it)

But you could do the following: Create a BANK. That prints out paper money in classical forms, with a serial number on it. And guarantes to print exactly the amount kept stored inside it's cold wallet. There is none such thing like a private key printed on them. Nothing to steal there, besides the note itself. As in classical money.

Why doing that, you might ask? Well, for several reasons.

  • It is possible, so it will be done, period. Stop argueing.
  • One can print nice pictures of historical ASIC devices on the front
  • It reaches a "niche market" out there, where a currency is needed for simple trades. Wares vs. cash right on spot.


I'm not thrilled about the idea, but numismatist is right. This will happen. I suspect bitcoin backed bank notes will reach more than a niche market. We can argue "with bitcoin you don't need to rely on a bank" all we like. The vast majority of people are fine with relying on banks, and they're already familiar with paper money. I suspect most of them think current paper money is backed by something. At least with bitcoin notes it would be easy to audit and ensure the notes are backed by something. I'm assuming the notes would be redeemable. The bearer of a note could take it to the bank and get the bitcoins.

Any other solution that involves trying to hide the private key will simply lead to ordinary people asking: What the hell is a "private key"?
72  Bitcoin / Bitcoin Discussion / Re: Bitcoin is not the answer for microtransactions; how to rebroadcast unconfirmed? on: August 08, 2014, 06:29:41 PM
I was using the ordinary Bitcoin-QT client (0.9.2.1). I used the debug console to create the transaction using the commands:

createrawtransaction ...
signrawtransaction ...
sendrawtransaction ...

I don't think Bitcoin-QT gives a way to choose which coins to spend using ordinary (GUI) methods.
73  Bitcoin / Bitcoin Discussion / Re: Bitcoin is not the answer for microtransactions; how to rebroadcast unconfirmed? on: August 07, 2014, 07:07:42 PM
I'm glad your problem seems to be resolved. I've had a similar problem since April 23 -- i.e., over 3 months. I managed to resolve it. I'll share it in case it helps someone in the future.

On April 23 I sent a small transaction from myself to myself. I didn't include a fee. Maybe I was cheap or maybe I forgot. I don't remember. I know the confirmation wasn't urgent. Well, it had been sitting in my wallet "unconfirmed" since then -- for over 3 months. At some point I tried the things described in this thread: rebroadcast with a fee, but it wouldn't get pushed onto the network because it looked like it never would. I waited for the transaction to "fall off" the network so I could resend it, but when I checked every few weeks it was still on blockchain.info as "unconfirmed."

Yesterday I had an idea: Spend the output of the unconfirmed transaction to myself again, but this time with a fee. I thought maybe a miner would confirm the first transaction in the hopes of being able to confirm the next one (the one with the fee). It worked -- and in a way I didn't know possible. Both of the transactions were confirmed in the same block. I didn't know a block could include two transactions, one of which spends from the output of the other, but apparently it's possible.

Conclusion: If there is a transaction that won't confirm due to a low fee, and you are the intended recipient, then just spend the output to yourself with a fee.

Here's the original transaction that was sent in April and confirmed today:

https://blockchain.info/tx/17f723bc265ebbeef77b2b081e29985c30b737025ed6a6547842d3c24d023797

Here's the second transaction confirmed in the same block (314320) with a fee of 0.0004827:

https://blockchain.info/tx/730546e11c79a3399f1fe7f617a7d4ff28edae1c7732180307ca84c2f1e63af2

And that's the story of how I got back my two mbits from 3.5 months of limbo.
74  Bitcoin / Development & Technical Discussion / Re: bitcoind won't start; runs out of memory on: August 01, 2014, 08:56:54 PM
I also have txindex=1. I should've mentioned that in my original post. I don't know if that affects memory usage, but it wouldn't be surprising.
75  Local / Treffen / Re: Stammtisch/Treffen Saarbrücken, Saarland on: July 31, 2014, 08:21:29 PM
Ich glaube wir Sonntag treffen wie jedes erste Sonntag in die Monat: Old Murphy's 17:00.

I expect we'll have the usual Saarbruecken Bitcoin meetup on Sunday, the first Sunday of the month, at Old Murphy's 5pm.
76  Bitcoin / Development & Technical Discussion / Re: bitcoind won't start; runs out of memory on: July 30, 2014, 08:09:23 PM
I created a 1GB swapfile (using dd) and added it as swap space.

bitcoind runs again! Thanks!
77  Bitcoin / Development & Technical Discussion / Re: bitcoind won't start; runs out of memory on: July 30, 2014, 07:51:50 PM
Thanks for the clarifications and suggestions everyone.

I tried running it with maxconnections=1, but this also ran out of memory.

I hadn't even considered creating a swap file on my own, so it wasn't a silly question at all.
I have root access, so I tried. My VPS provider was prepared:

Code:
fallocate -l 1G /swapfile
fallocate: /swapfile: fallocate failed: Operation not supported

Edit: I now realize I might be able to do this in other ways than fallocate. I'll keep working on it.
78  Bitcoin / Bitcoin Discussion / Re: ARG Puzzle with 3.5 BTC Private Key Prize, Game Over on: July 30, 2014, 05:31:06 PM
once again: why is there a GATEway for darkwallet and a GATEkeeper just happens to have won?

And mathGATE kept pushing their crappy treasure hunt? It's a gate-spiracy! This is bigger than Watergate. It's gategate. All your gates are belong to us.
79  Bitcoin / Development & Technical Discussion / Re: bitcoind won't start; runs out of memory on: July 30, 2014, 05:10:09 PM
Oh well. No full node for me.

I'm curious: Does anyone know why it worked for the past 3 months, but then stopped working now? My best guess is that the main use of RAM is the utxo set. Has the number of utxo's increased recently?

80  Bitcoin / Development & Technical Discussion / Re: bitcoind won't start; runs out of memory on: July 30, 2014, 06:32:11 AM
Thanks for the help. The VPS is running Ubuntu 12.04.4 LTS. According to free -m there is no swap space, which might be causing the problem.

I don't get to the point where I can call bitcoind getinfo because bitcoind -daemon is still in the initial phase before it dies. After calling bitcoind I can use top or free -m to watch the memory usage climb until it hits 1GB and dies.

Pages: « 1 2 3 [4] 5 6 7 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!