Bitcoin Forum
July 31, 2015, 01:23:04 PM *
News: New! Latest stable version of Bitcoin Core: 0.11.0 [Torrent]
 
  Home Help Search Donate Login Register  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 [9] 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 ... 112 »
161  Bitcoin / Bitcoin Discussion / Re: Who the hell is Max Keiser? on: March 16, 2014, 11:55:52 PM
he is a good guy with solid intentions and awareness.
162  Bitcoin / Development & Technical Discussion / Re: sx command line utilities - Empower The Sysadmin With Bitcoin Tools on: March 16, 2014, 11:52:21 PM
ok, if you do then run the latest script. I've made lots of changes.

FYI on the latest install script it fails to remove the package libzmq on debian because it doesn't exist, only libzmq-dev does in the standard repositories (or at least on mine install)..  removing that item from the script corrects the issue.

Weird, because I'm testing on Debian Wheezy virtual machines. I'll look further, thanks.

Edit: OK, I've changed it to a wildcard.
163  Bitcoin / Development & Technical Discussion / Re: sx command line utilities - Empower The Sysadmin With Bitcoin Tools on: March 16, 2014, 08:11:44 PM
ok, if you do then run the latest script. I've made lots of changes.
164  Bitcoin / Development & Technical Discussion / Re: sx command line utilities - Empower The Sysadmin With Bitcoin Tools on: March 16, 2014, 06:34:05 PM
I'm using Debian Wheezy, what are you using? When did you install it? When did you start the daemon? Are you using an SSD? I would recommend an SSD because a lot of the code assumes you're using SSDs (0 seek times) as I believe they're the future of storage.
165  Bitcoin / Development & Technical Discussion / Re: sx command line utilities - Empower The Sysadmin With Bitcoin Tools on: March 16, 2014, 04:03:01 PM
have you configured it to only connect to your bitcoind? if so, how many blocks does your bitcoind have? use ./bitcoind getinfo to see. if bitcoind has the correct number of blocks then try restarting obelisk and/or restarting bitcoind. does it start syncing?
166  Bitcoin / Development & Technical Discussion / Re: sx command line utilities - Empower The Sysadmin With Bitcoin Tools on: March 16, 2014, 01:20:09 PM
If anyone is using unSYSTEM Obelisk servers, then they will be upgraded today (Sun 16 March). If you experience problems with the new unSYSTEM servers, then upgrade SX:

Code:
$ wget http://sx.dyne.org/install-sx.sh
$ sudo bash install-sx.sh

or

Code:
$ wget http://sx.dyne.org/install-sx.sh
$ bash install-sx.sh /home/genjix/usr/

You also have the option to run a different server with an older version of Obelisk, although I'll be encouraging operators to upgrade soon. List of servers: https://wiki.unsystem.net/index.php/Obelisk/Servers - let me know if you have a server to add to the list.
167  Bitcoin / Development & Technical Discussion / Re: sx command line utilities - Empower The Sysadmin With Bitcoin Tools on: March 16, 2014, 11:59:14 AM
I'm now on my fifth attempt using 2 different servers (one a pretty much clean Debian VM and one an established server).. every time I get nearly to the end of the blockchain sync it just seems to sit around not receiving new blocks and spewing reams of errors such as below. I'm assuming blockchain database corruption but it always seems to be somewhere in the 27#### block range (I've just noticed this). Is this normal? Is there maybe something about this range of blocks, was that when someone was spamming the blockchain? Getting a bit frustrated here sapping so much time and bandwidth and still haven't got a sync'd copy to play with. I don't want to download a torrent copy.


WARNING: Error storing memory pool transaction c0c958698d61b260a885115a7e2ccec1a25c8a121c0da9ec6165f0ce11920c9b: Spent input not found


Nope it looks fine. Those errors aren't a problem. Example: memory pool isn't full yet and there's txs depending on other txs in the mempool that aren't yours. It's normal. I'll make the wording sound less extreme.

Important is that you're able to run 'sx fetch-last-height' and the block height matches blockchain.info or somewhere else.

I need to document these tools better. Sorry about that. I'll be making efforts towards that goal as documentation is important.
168  Bitcoin / Bitcoin Discussion / Re: I made this video on the ostracism happening against Bitcoin libertarians on: March 15, 2014, 09:37:08 AM
common production just makes sense. why work for anyone else but yourself. it's the only sustainable economic model and bitcoin empowers it. esp with multisig and other tools. i see many possibilities for using markets in this way.
more than anything we can invest in technology and better industrial tools rather than buying tvs or other good given to us- long term we all end up better together.

http://opensourceecology.org/wiki/Practical_Post-Scarcity_Video

instead of small toys (porsche, luxury apartment .etc), have the best and biggest toys (industry, farms, techno infrastructure, production, large scale construction). it's my aim Smiley
https://wiki.unsystem.net/index.php/UnSYSTEM/OpenSource_city

Mi staras kun vi, amiko!

En pli ol unu maniero ni estas samideanoj.



Dankon kaj mi kun vi, unu al la alia.

Malfelicxe la plej bonaj ideoj ne cxiam sukcesas. Sed Bitmono estas bonega ideo kiu sukcesos.
169  Bitcoin / Bitcoin Discussion / I made this video on the ostracism happening against Bitcoin libertarians on: March 14, 2014, 12:54:40 PM
https://www.youtube.com/watch?v=cRAYT2gaAqw

reddit thread if you want to help spread this message by upvoting:
http://www.reddit.com/r/Bitcoin/comments/20ect1/i_made_this_video_on_the_ostracism_happening/
170  Bitcoin / Development & Technical Discussion / Re: sx command line utilities - Empower The Sysadmin With Bitcoin Tools on: March 12, 2014, 05:14:52 PM
Hey everyone,

 The new Obelisk has support for server-client encryption and
signing using ed25519 crypto. The client can specify a key, and the
server can specify which client pubkeys it will accept (or all) and a
whitelist of IP addresses.

See this config file for reference:

https://github.com/spesmilo/obelisk/blob/master/src/worker/worker.cfg#L24

The install-sx.sh script will be broken because of new dependencies .etc so I will fix it now. Sorry for any difficulties.
171  Bitcoin / Development & Technical Discussion / Re: sx command line utilities - Empower The Sysadmin With Bitcoin Tools on: March 12, 2014, 12:47:05 AM
Sorry about this. The install script should install those packages but the build stuff for sx and the rest of the libbitcoin-related tools need some work.
172  Bitcoin / Bitcoin Discussion / Re: Iran and Bitcoin.... on: March 11, 2014, 11:36:31 PM
iran is very important. if they said fuck it and allowed btc trade it would undermine US interests more than their own, but it would loosen the death grip of the suicidal regime.
173  Bitcoin / Bitcoin Discussion / Re: So do Bitcoiners actually claim the foundation wasn't infiltrated? on: March 11, 2014, 01:04:08 PM
Basically I wouldn't be worried about some conspiracy. I'd be more worried if the developers represent corporate interests and are controlling development. There's a lot of deep difficult decisions in the code where it's not clear one path or another. If your agenda is even slightly corrupted then you will take the small decisions to benefit corporations over the black market/small businesses/p2p transfers. Corruption is not one big thing but many small decisions. Take the payments protocol as an example which uses CAs- it doesn't benefit small businesses, p2p transfers or the black market only corporations to reduce payment friction for them. That's why it's important to support alternative implementations that give a voice to empower different segments of the community as part of the development process.

Anyone interested in alternatives should check out what we're doing with darkwallet - we have our own alternative & full stack of BTC software: https://bitcointalk.org/index.php?topic=372390.0
174  Economy / Services / Re: I will pay 0.15 to first person who dox Leah McGrath Goodman on: March 06, 2014, 10:16:44 PM
blaa blaa blaa walls of text. this is internet justice at its finest. anyone who leaks her info if they post an address will get lots of donations guaranteed. i don't know what went through her crazy mind to think this was ok. people need to call her and let her know it was wrong.

"this defenseless eccentric old man has $400m and he lives here <photo him> <photo house>."
175  Bitcoin / Bitcoin Discussion / Re: **Breaking news** Satoshi Nakamotos identity revealed on: March 06, 2014, 01:04:19 PM
Way to reward our liberator. Irresponsible.
176  Bitcoin / Alternative clients / Re: libbitcoin on: March 06, 2014, 12:26:45 AM
Maybe someone can help me with this. I'm having a problem building libbitcoin-bindings on Arch Linux. I PMed genjix, but he hasn't gotten back to me yet. (I'm sure he's very busy.)

Here is the output I get when running make. I symlinked include/bitcoin/ from the libbitcoin source directory into the current directory. Also, I had to change the calls to pkg-config in the Makefile to use python3 explicitly.

Googling around led me to this closed GitHub issue for another project. Maybe it's related? I don't know how to duplicate the fix, though.

Thanks.

The bindings are old and unmaintained. Sorry.

If you want to use Obelisk from Python, we have a pure Python library:

https://github.com/darkwallet/python-obelisk
177  Bitcoin / Development & Technical Discussion / Re: Lightweight ID verification for payment protocol v1.1 on: March 05, 2014, 04:24:25 PM
lol mike hearn wanted to use passports for auth between bitcoin nodes. what a newb.
178  Bitcoin / Bitcoin Discussion / Re: Is Gavin Andresen Sincere when he says he cares deeply about privacy in Bitcoin? on: March 03, 2014, 02:00:10 AM
yeah wicked! lets do it. we have lots of smart people and some nice projects emerging.
179  Bitcoin / Development & Technical Discussion / Re: META: Would you like this board be divided into child-boards? on: February 21, 2014, 10:18:17 PM
no, there's already too many subforums to wade through on this forum. i don't have time to open tons of tabs all the time.
180  Bitcoin / Development & Technical Discussion / Re: SX with 2-of-2 MULTISIG on: February 21, 2014, 07:47:15 PM
I followed your instructions but put the zero at the beginning and generated a valid 2of2 spend:

https://blockchain.info/tx/086bd5c500021f007d2e77d8dc7fcbe200dca4f7957eef7ff1f788996a5381c8

Code:
2010  cat tx_spending.tx | sx showtx
 2011  SIGNATURE_1=$(cat tigra-pvt.key | sx sign-input tx_spending.tx 0 $(cat msig.script))
 2012  SIGNATURE_2=$(cat dipspb-pvt.key | sx sign-input tx_spending.tx 0 $(cat msig.script))
 2013  echo $SIGNATURE_1
 2014  SIGNATURE_1=$(cat tigra-pvt.key | sx sign-input tx_spending.tx 0 $(cat msig.script))
 2015  SIGNATURE_2=$(cat dipspb-pvt.key | sx sign-input tx_spending.tx 0 $(cat msig.script))
 2016  echo $SIGNATURE_1
 2017  echo $SIGNATURE_1
 2018  echo $SIGNATURE_2
 2019  INPUT_SCRIPT=$(sx rawscript [ $SIGNATURE_1 ] [ $SIGNATURE_2 ] [ $(cat msig.script) ] )INPUT_SCRIPT=$(sx rawscript [ $SIGNATURE_1 ] [ $SIGNATURE_2 ] [ $(cat msig.script) ] )
 2020  INPUT_SCRIPT=$(sx rawscript [ $SIGNATURE_1 ] [ $SIGNATURE_2 ] [ $(cat msig.script) ] )
 2021  INPUT_SCRIPT=$(sx rawscript zero [ $SIGNATURE_1 ] [ $SIGNATURE_2 ] [ $(cat msig.script) ] )
 2022  echo $INPUT_SCRIPT
 2023  echo $INPUT_SCRIPT | sx showscript
 2024  sx set-input tx_spending.tx 0 $INPUT_SCRIPT > tx_spending_signed.tx
 2025  cat tx_spending_signed.tx
 2026  cat tx_spending_signed.tx | sx showtx
 2027  cat tx_spending_signed.tx
 2028  cat tx_spending_signed.tx | sx validtx
 2029  cat tx_spending_signed.tx
 2030  cat tx_spending_signed.tx | sx showtx
 2031  history
Pages: « 1 2 3 4 5 6 7 8 [9] 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 ... 112 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!