Bitcoin Forum
April 24, 2014, 05:53:37 AM *
News: Due to the OpenSSL heartbleed bug, changing your forum password is recommended.
 
  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 ... 107
61  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.
62  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
63  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>."
64  Bitcoin / Bitcoin Discussion / Re: **Breaking news** Satoshi Nakamotos identity revealed on: March 06, 2014, 01:04:19 PM
Way to reward our liberator. Irresponsible.
65  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
66  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.
67  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.
68  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.
69  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
70  Bitcoin / Development & Technical Discussion / Re: OP_RETURN and non-standard transactions on: February 21, 2014, 07:03:43 PM
Well, it's not *supposed* to, and Luke-Jr considers it a bug if it does.

Quote
[09:09:16] <maaku> Luke-Jr: does Eligius accept OP_RETURN data outputs?
[09:10:23] <Luke-Jr> maaku: not intentionally.
[09:11:01] <maaku> you've fixed it right, so it no longer does?
[09:11:08] <Luke-Jr> not sure
[09:13:40] <Luke-Jr> maaku: if it works right now, hopefully we will fix that soon

ok thanks for clarifying
71  Bitcoin / Bitcoin Discussion / Re: Anonymity on: February 21, 2014, 06:46:54 PM
anonymity breeds culture and vibrancy:

http://chrishateswriting.com/post/76431353368/the-anonymity-i-know

this drive to normalise and purify our activity leads to groupthink and acceptance of imposed limitations.

protecting the small guy is empowering voiceless communities.

for a deeper explanation of the ethos:

https://en.wikipedia.org/wiki/Hacker_ethic#The_hacker_ethics
72  Bitcoin / Development & Technical Discussion / Re: OP_RETURN and non-standard transactions on: February 21, 2014, 12:36:14 PM
Eligius does not accept OP_RETURN outputs.

yes they do.
73  Bitcoin / Development & Technical Discussion / Re: Stealth address with SX (anonymous payments) on: February 16, 2014, 09:31:42 AM
Thanks, we're trying to be organised but it's tricky sometimes.

Basically the main production repos are:

https://github.com/darkwallet
https://github.com/spesmilo/

My personal repo contains mostly experimental/testing stuff which later enters into the above repos as it matures (stufflike Obelisk, stealth, databases, .etc). My toys:

https://github.com/genjix/

The wiki contains a lot of our internal documentation for our projects:

https://wiki.unsystem.net/

Also our IRC channel is important- Freenode #darkwallet (would be cool to see you on there and coordinate). We are offering free bouncers BTW if anyone wants one: https://wiki.unsystem.net/index.php/DarkWallet/Bouncer

The unSYSTEM website should be our landing page, and we plan to syndicate a lot more stuff there but it needs work on both content and tech side (https isn't working):

http://unsystem.net/

d3 (admin for our projects) has setup https://libbitcoin.org/ now and I plan to move the website there, but we need to get the builds working, easy for me to push updates .etc

We also have mailing lists:

https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/unsystem
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin
https://lists.unsystem.net/cgi-bin/mailman/listinfo/darkwallet

We definitely need to organise all these resources better. Would be cool to talk on IRC so we can plan if you have some ideas, and we can coordinate with the admin / other people.
74  Bitcoin / Development & Technical Discussion / Re: SX with 2-of-2 MULTISIG on: February 15, 2014, 01:49:52 PM
Hey this drove me a bit mad trying to track down the problem and I ended up having to hack the source. You need an extra 'zero' opcode at the start of the signatures for the input script:

Code:
hash: 18ef65bb0e8c26dd9f02866161fc8f92f49b6a33b63b8310d645b9008ec6c7ff
version: 1
locktime: 0
Input:
  previous output: 07acadc2e7042f4a43305d08fd03c66800155b7ecb6ac56c3395fd906a8ed69a:1
  script: zero [ 30440220587a9cdb4847d4a7586ed25f95a21d8cae1db64b579bb11eb5c14c033ece8bba022027c1e8395470bc0c7be1d792c33f52bcca27e4bd027231f93a74bb5dddcabbc501 ] [ 3045022100b8e9d83ea79bc97188b6ed7072bb361a9b9d00e35336a0b1e444a4a39ce75410022039da58cbc38e55c9dd89f4990ea8a7b8f18d3c6d9f809ff1219382e4c5894eb901 ] [ 522102fb034f6e3f9608a99bba7627c3eb5527102335df46262563681b6c53cc7876952102fcb4a15e1a47eb2e4b4684e18a76a9702e254816d6bad3b2aee141742ebd74cc52ae ]
  sequence: 4294967295
  address: 3KnHCJAymuz9mzMQBeHp6Tjvo2kqr7giug
Output:
  value: 90000
  script: dup hash160 [ a387ba64648b2c78b38d5278a43f0291a06458f0 ] equalverify checksig
  address: 1Fufjpf9RM2aQsGedhSpbSCGRHrmLMJ7yY

Then it should work.

Code:
$INPUT_SCRIPT=$(sx rawscript zero [ $SIGNATURE_1 ] [ $SIGNATURE_2 ] [ $(cat msig.script) ] )
75  Bitcoin / Development & Technical Discussion / Re: Stealth address with SX (anonymous payments) on: February 14, 2014, 11:16:40 PM
good analysis. not many people are reading between the lines or thinking that far ahead. history teaches us much.
76  Bitcoin / Alternative clients / Re: libbitcoin on: February 14, 2014, 11:14:28 PM
yes, if I have an SSH and some help, I would make sure everything compiles as I develop the tools.

I have an admin who can provide the environment and support, but he will need assistance to setup all the dependencies and build system. Once everything is ready and I can try to compile libbitcoin (coordinating with you), then I can see what fixes need (if any) to be made to the code and maintain that by having my admin compile it every so often.

Red Emerald does mac ports here, and I'd need help for packaging. I'd just guarantee the code compiles + works.

I'm on Freenode IRC #darkwallet as genjix (admin is d3), or alternatively my email is genjix at riseup dot net (cc d3 at riseup dot net)
77  Bitcoin / Development & Technical Discussion / Re: Stealth address with SX (anonymous payments) on: February 14, 2014, 09:08:04 AM
thx for flattery. I also take donations: 1Fufjpf9RM2aQsGedhSpbSCGRHrmLMJ7yY

Stealth blockchain stuff is now part of libbitcoin, obelisk .etc

More info: https://wiki.unsystem.net/index.php/DarkWallet/Stealth#Toys

You can lookup the transactions in the blockchain, do the comparisons and find candidate results.

Documentation about everything is on the wiki for developers.

Code:
$ sx fetch-stealth
Usage: fetch-stealth NUMBER_BITS BITFIELD [FROM_HEIGHT]
$ sx fetch-stealth 2 deadbeef
DEBUG: ephemkey: 024398667c6a11652ae80fe6370e140cc67d4f82fb8310122cdaddae1524dad9e0 address: 1Nw1EKu8Y6mPGhMGyrKPS9TZWDyTPLvi8a tx_hash: 6a6246ccc7cb9427efee85dd3c7b80164f8a61213a7ce357b8cfd3816f59aab9
DEBUG: ephemkey: 02828c82feeae6ea5526e1b17adf3a7e9a1ee53680fc0ba651a3e7c1a99529ef24 address: 1QJSNUqt8HRygcNvbyYHQw5NizMCBkixsb tx_hash: 75885e50418cee0e527316df1f740ef6bc6b60a4b325c6d8d20e00a053cd27f9
DEBUG: ephemkey: 03a3e941099eda82cee7727e238e34283611e71debe063ed5029b51336060de080 address: 1KnByqTSjWbh5gb2K74Nkdf6oU5VMtfJqf tx_hash: 6deba5f43c85d881fa88fd40f53ab2c825682d4829db0154982ddf9f60a9a0c7
DEBUG: ephemkey: 024b4d9a7564644deb94743872e6823f87c1ce8cca7c2ba84cd926dea5498a0a53 address: 14DcERFvDPYTr1PHqphqvQuawvAoFTsKgH tx_hash: ba058ad8330e56b5cb18c08d98c465a91d7ce4d1bc5ac10f1384a0619a3559f4
78  Bitcoin / Alternative clients / Re: libbitcoin on: February 14, 2014, 09:05:56 AM
thanks lewsig.

Stealth blockchain stuff is now part of libbitcoin, obelisk .etc

More info: https://wiki.unsystem.net/index.php/DarkWallet/Stealth#Toys

You can lookup the transactions in the blockchain, do the comparisons and find candidate results.

Documentation about everything is on the wiki for developers.

Code:
$ sx fetch-stealth
Usage: fetch-stealth NUMBER_BITS BITFIELD [FROM_HEIGHT]
$ sx fetch-stealth 2 deadbeef
DEBUG: ephemkey: 024398667c6a11652ae80fe6370e140cc67d4f82fb8310122cdaddae1524dad9e0 address: 1Nw1EKu8Y6mPGhMGyrKPS9TZWDyTPLvi8a tx_hash: 6a6246ccc7cb9427efee85dd3c7b80164f8a61213a7ce357b8cfd3816f59aab9
DEBUG: ephemkey: 02828c82feeae6ea5526e1b17adf3a7e9a1ee53680fc0ba651a3e7c1a99529ef24 address: 1QJSNUqt8HRygcNvbyYHQw5NizMCBkixsb tx_hash: 75885e50418cee0e527316df1f740ef6bc6b60a4b325c6d8d20e00a053cd27f9
DEBUG: ephemkey: 03a3e941099eda82cee7727e238e34283611e71debe063ed5029b51336060de080 address: 1KnByqTSjWbh5gb2K74Nkdf6oU5VMtfJqf tx_hash: 6deba5f43c85d881fa88fd40f53ab2c825682d4829db0154982ddf9f60a9a0c7
DEBUG: ephemkey: 024b4d9a7564644deb94743872e6823f87c1ce8cca7c2ba84cd926dea5498a0a53 address: 14DcERFvDPYTr1PHqphqvQuawvAoFTsKgH tx_hash: ba058ad8330e56b5cb18c08d98c465a91d7ce4d1bc5ac10f1384a0619a3559f4
79  Bitcoin / Alternative clients / Re: Mycelium Bitcoin Wallet on: February 13, 2014, 12:49:13 AM
Hi MyCelium people, good work on trading stuff but I heard you're using a tx radar for giving confidence to traders who receive BTC.

I think this is an extremely bad idea, as txs can be replaced after 100% propagation has been achieved by sending higher fee txs to replace the one you made. This attack only needs to work 1% of the time to be profitable but in reality can work much more (maybe even 100%) if pulled off correctly. You don't even need to tell the whole BTC network, just a few specific miners.

For instance if I submit my replacement tx to eligius using their web interface, then make the trade before eligius mines a block, if eligius mines a block it won't include the tx that got 100% propagation because that would've been rejected by eligius.

I suggest you remove this feature, and only using it for senders of BTC (not recipients).

The localbitcoins thing otherwise looks excellent. Thanks for this contribution. I don't mean to beat on this parade and be so negative, I like your work.
80  Bitcoin / Development & Technical Discussion / Re: Stealth address with SX (anonymous payments) on: February 11, 2014, 07:19:12 PM
thanks for appreciation of my work, it's a nice donation. as an opensource coder, I love it when people to steal my work.

e4xit- yeah the deadbeef is a 4 byte nonce. see:
https://wiki.unsystem.net/index.php/DarkWallet/Stealth

it's a (currently) unused scalability feature that will be enabled later once the number of stealth txs goes up.
people will be able to reissue stealth keys and narrow the space of possible candidate txs from the blockchain to reduce the processing and traffic they need. in the beginning we might not even split the space so everyone's transactions can protect each other.
normally you should brute-force different values until you find a hash where the first N bits matches what's specified by the stealth address. Since I'm using N=0, it doesn't matter what I put there - I'm using this for developing the server side stealth features in obelisk.

it's a very smart feature from peter todd. bloom filters is not scalable, efficient nor really that private.
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 ... 107
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!