Amir Taaki. All about cryptocurrency - BitcoinWiki
Cryptocurrency Exchange to Buy Bitcoin and Ether Gemini
PHP developer intro - BitcoinWiki
Re: [unSYSTEM] Dark Wallet: A Radical Way To Bitcoin
CoinCode: infos on coin/blockchain code, tools, and tech.
CoinCode in my mind is a specialized place in that I would like to discuss all things coin/blockchain that pertain to code, tools/software, and technology. This is a partly product of me having to dig through posts to find the ones with code blocks in /bitcoin, but also to help perpetuate the open and free ideals that the blockchain/bitcoin code were born from.
Come on people, ether raises 26,000+ BTC! then other important projects like dark wallet raises little scratch.
Dark wallet and anon coin mixing is sooooooo important for "legitimate" business just as much as iligitamate businesses because no business owner wants thier competitors to figure out income or who a supplier is or how much they are paying for supplies. Just normal business.
It is important for bitcoins future to be anon by default.
“We want highly skilled, hard working people that are fans of bitcoin as a technology, and perhaps less as a movement – you need to be able to separate business from politics if you want to operate in the highly regulatory space of financial services.” It is always hard to attract talent to startups, and it is even harder to attract talent to a startup in a new ‘risky’ technology.
Darkwallet has the opposite problem. We WANT politicised highly motivated individuals that think for themselves and are honest with us. We have lots of talent offering us their help from designers at the top of their field to highly skilled programmers. We just don't have the resources to pay people, and so everyone chips in a little of their time and things inch slowly along. It's easy for me to sell the project, and take investor money. But I want to keep this project pure to its goals and integrity, and working for the community instead of selling it off to the highest bidders for their profit. I want Bitcoin users to profit from this project. We need to raise 40 BTC to make the release, and then we'll be in a strong position as a project to raise capital from multiple sources to fund development. So don't be shy, we will deliver the best production ready wallet with unmatched technology on all fronts. Tools to create your own DAC, launder money to your own private super tax haven, a smooth beautiful experience and the best in instant yet private blockchain technology (that no other wallet has). Who https://wiki.unsystem.net/en/index.php/DarkWallet/Project_multisig_fund Keep Darkwallet in your hands.
So it's no secret that BIP101 and similar hard fork proposals have been a controversial topic, especially here in /bitcoin. I've seen theymos called out for censorship time and time again, and while I don't condone what he did, I've started to understand it. When I first heard about the proposals to increase the block size, I was skeptical at best. I had run a full node at home for some time, and was beginning to worry about the large footprint it was starting to take on my hard drive. Of my laptop. So I wasn't an always on full node, but I was frequently on. And I was running out of space. Then came the bip101 centralization FUD. About the same time, I started to read about lighting networks, and asked some questions about it and the blocksize increase on this forum. I'll admit I got a bit-on for lightning as I read about it (and more recently when I read about a similar idea to lightning, but somehow different [and I can't remember the name or the whitepaper where I read it]). Then came the lightning centralization conspiracy, and I became a skeptic. I think it was core v0.11 where they introduced blockchain trimming, I started to feel a little better about the idea of larger block sizes. I can always trim the size down, right? I told myself. So maybe bip101 wasn't so bad? Hard drives are always getting bigger, so shouldn't that be enough? I think I was swayed to Mike and Gavin's arguments when I watched them in a video talk about how they are being oppressed about this, and decided I was on the side of blocksize increase. Then came the big dogs hailing their support; this oddly made me feel better about it, where I'm naturally skeptical of large corporations' endorsements. BIP101 wont do any harm anyway, right? I think I was wrong. I asked myself What are the consequences of increasing the blocksize over time? Do we honestly expect the average user to be able to keep up with an ever-increasing block size? I know I move slower than that; I don't buy a new computer every two years. Four-to-six, maybe. But I've already been drowned out of using my laptop to keep an up-to-date blockchain (I know it probably wasn't a good idea in the first place). Where will the full nodes go? Mike and Gavin are centralization fanboys, I think it's fair to say. Sorry, guys, if I'm mislabeling you - I'm pretty sure I've seen you more or less say that outright, though. I'm not. Like the now-defunct author of DarkWallet, Amir Taaki has said, there is no political neutrality here. Bitcoin is meant to take power from central hands, and divide it amongst the people. Now, I have no idea where genjix went, but I've found myself agreeing with him on this - bitcoin isn't a good payment processor. Now, I'm not sure if it was meant to be - or needs to be. There are already many options proposed to add decentralized (even distributed) payment processing - that can scale - that don't necessarily require a blocksize increase. Now I'm realizing that bip101 is a proposal that will only serve to transfer wealth and power to the largest companies. I'm finding myself convinced that full nodes will be forced onto servers and data centers, and I disagree with Gavin and Mike that that is a good thing. I think that will kill bitcoin and its value. Here's how I'm starting to see it. The blockchain is like a fast version of bank transfers. It sucks for transfering small amounts of money over many transactions, but it didn't need to fulfill that. No one asked your bank to be a paypal, or a visa. I really believe that we can build on top of where the blockchain is right now, without chainging block sizes again, and even relieve stress without decreasing the amount of transactions capable. The best ideas for new apps are yet to come. We can build tools that enhance bitcoin, and utilize it without changing its fundamental purpose and message. Kissing up to large corporations and governments will not make bitcoin a better place. They have enough power - lets work on increasing ours. tl;dr Please, don't adopt bip101. The other alternatives will come soon enough.
Combining SPV and Stealth addresses | Henning Kopp | May 04 2017
Henning Kopp on May 04 2017: Hi all, Recently I think a lot about combining Stealth addresses with SPV but I did not come to a satisfying conclusion, so I post this as a challenge to the wider community. Maybe you have an idea.
Explanation of SPV
In SPV a thin client puts his public keys in a bloom filter and asks a full node to give him Merkle proofs of all transactions whose pubkey are in the bloom filter. Since a bloom filter has a lot of false positives depending on the parameters, this gives privacy to the thin client, since the full node cannot detect if a specific transaction belongs to the thin client. This is cool if you want to use Bitcoin on your smartphone.
Explanation of Stealth Addresses
Stealth addresses on the other hand enable receiver privacy. The sender of a transaction derives a one-time pubkey to which he sends the money. The receiver can check if the money was sent to him and recover the one-time private key. This is cool, since an observer cannot decide if two payments belong to the same recipient. Further the recipient needs only to have one pubkey. For a more formal explanation see https://github.com/genjix/bips/blob/mastebip-stealth.mediawiki#Reuse_ScanPubkey I will use their notation in the following.
My line of thought was to combine stealth addresses with spv, so that I can use stealth addresses on my smart phone without losing privacy. Basically to check if a payment belongs to a pubkey (Q,R), the full node needs to check if R' = R + H(dP)*G for each transaction. For this it needs the private scanning key d. This sucks, since when I give my d to a full node, he can link all my transactions. For an online-wallet this may be okay, but not for thin client synchronisation.
In the following I detail some ideas of me which did not work. It does not suffice to have a Bloom filter and check if d is contained since there is no way to recompute d from the equation. If there were a way to recompute d, the scheme would offer no privacy, since anyone could compute the private scanning key d and scan for payments. So, if we modify the scheme we need to be sure that d is kept private. Multiparty computation may be possible in theory. The full node and the thin client could collaboratively check R' = R + H(dP)*G, where d is the private input of the thin client and R, R',P is provided by the full node. But this is costly and they need to do it for each transaction. It may be more costly than simply setting up a full node. I do not think that some kind of search functionality without leaking the search pattern (PIR?) would work, since the full node needs to compute on the data it has found. And further it needs to retrieve the whole Merkle proofs. Any better ideas? Best, Henning Henning Kopp Institute of Distributed Systems Ulm University, Germany Office: O27 - 3402 Phone: +49 731 50-24138 Web: http://www.uni-ulm.de/in/vs/~kopp original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014259.html
sx Bitcoin utilities (new installation instructions and information inside)
Hi! My aim with this project is to provide a set of modular Bitcoin commandline utilities, that admin types can engage with Bitcoin functionality without having to write code. By chaining all these commands together in different ways, you can do offline transactions, maintain a wallet, work with deterministic keys, ... It would be cool to see Bitcoin wallets written in bash script using these tools to handle the core functionality. I believe the more we give good tools to the community, the more we can decentralise development and increase access to the core technology for all types. Use this bash shell script to install sx: http://libbitcoin.dyne.org/install-sx.sh
Now send some funds to your address (0.01 BTC). In this example we will send the funds to 13Ft7SkreJY9D823NPm4t6D1cBqLYTJtAe.
100000 Satoshis (0.001 BTC) in total. 90000 Satoshis (0.0009 BTC) to send. 10000 Satoshis (0.0001 BTC) for the fee.
Use blockchain.info (or the history tool provided here) to lookup the output for this address. Note down the transaction hash and transaction index. Here is a screenshot of blockchain.info: http://i.imgur.com/dZvqJIV.png We can see the tx hash is: 97e06e49dfdd26c5a904670971ccf4c7fe7d9da53cb379bf9b442fc9427080b3 And there is a single output at index 1 that we want to spend (the 2nd one for 0.001 BTC). Construct the transaction:
Because there is 100000 Satoshis going in, but only 90000 Satoshis out, the remaining 10000 Satoshis (0.0001 BTC) will be taken by the Bitcoin network as a fee. This is how fees work internally in Bitcoin. 'showtx' allows inspecting of tx files.
You can use either the master_public.key or the wallet.seed for generating Bitcoin receive addresses. But you cannot use the master_public.key for generating the private keys for spending those Bitcoins.
For Electrum compatible 12 word seeds, use the mnemonic tool.
$ echo 148f0a1d77e20dbaee3ff920ca40240d | sx-mnemonic people blonde admit dart couple different truth common alas stumble time cookie $ echo "people blonde admit dart couple different truth common alas stumble time cookie" | sx-mnemonic 148f0a1d77e20dbaee3ff920ca40240d
The balance/history tools can then use a network connection to make requests against the load balancer.
It's possible to run as many backend workers as you like. The load balancer (obbalancer) will distribute requests evenly among the backends. Use worker-output.sh to view debug info from the worker. Each worker must have their own unique copy of the blockchain database. See the Obelisk config files in /uslocal/etc/obelisk/. The sx config file is stored at ~/.sx.cfg (there's an example at /uslocal/share/sx.cfg). You can change this configuration parameter using './configure --sysconfigdir=/etc/'. By configuring different workers and load balancers, you can run multiple setups on the same host. By default it is no pointing at my development server, but I will change this soon and migrate to a new host. Also I make no guarantees about stability or compatibility.
Love you guys! Support our DarkWallet project to help in this struggle for freedom
https://darkwallet.unsystem.net/ Support our project if you feel as we feel. It begins with a wallet, but so much more is possible. Having a decentralised uncensored Silk Road is fully within the realm of possibility, but first we need to underlying infrastructure in place for developers on top to innovate. Our job is to create those tools. It's difficult and stressful work, and I've been doing this for 3+ years now living off no money. But now we need additional resources to pay for common things like hardware and infrastructure that our group needs to work effectively. Nice picture in the background. I remember all those che t-shirts that the yuppies used to wear. Can't wait to see all the black-market, "blow-stamps", and bitcoin yuppie merchandise. genjix / amir
The story of CoinJumble: or Why you need more than a nice GUI to get adoption
About a year ago I had been thinking about coinjoin. I'd read gmaxwell's post and looked at some of the implementations like I taint rich!, Andytoshi's Coinjoiner and Genjix's Coinjoiner They needed people to have to want to do a coinjoin at essentially the same time. Given that bitcoin transaction volume peaked at about 1 tx/second then, it was quite unlikely that there would be someone else wanting to transact exactly the same amount as you. I thought this was the reason they were not getting adoption. Furthermore they needed centralized servers, Genjix's coinjoin server had already been taken down so I couldn't try his program. Also some of those applications required used command-line raw transaction, which many people were not comfortable with. If non-programmers could just have a point-and-click GUI they would use it. Build it and they would come, right? So I came up with the idea of a GUI application that had serialization format for raw transactions. The idea was people would share their transaction parts asynchronously. A lot like GPG ascii armor, the application made no assumptions about how the CoinJoin peers communicate, only that they can send each other transaction parts in a private way. They could post them on Tor hidden service forums, Bitmessage chans, I2P eepsites, Freenet pages or shared some other way. I called it CoinJumble, it had an infographic explaining how to use it And... nobody used it. I suppose it would be tedious to post adverts everywhere like "Looking for a few coinjoin partners for 0.523453btc !". Also there was the problem that it exposed users to raw private keys. A little later, oakpacific, waxwing and I publicly did a coinjoin on reddit to show the world how to use CoinJumble. (Someone later combined their change with their coinjoin output and so ended up linking his addresses together again) Some of these ideas, as well as me looking at DarkWallet, gave me the ideas needed to come up with JoinMarket, which doesn't even have a GUI yet and people still use it every day. By the way, CoinJumble turned out to be very useful in debugging raw transactions. It was far easier, quicker and more informative to put a txhex into the GUI than to use decoderawtransaction or some website.
$ ./bitcoin-cli listaccounts # show list of accounts and various info for each one $ ./bitcoin-cli getaccountaddress user889 # get an address to receive money to that is unique for the account user889 $ ./bitcoin-cli getbalance user889 # get the sum of all the money in the addresses owned by the account user889 Gemini is a regulated cryptocurrency exchange, wallet, and custodian that makes it simple and secure to buy bitcoin, ether, and other cryptocurrencies. Amir Taaki (born 6 February 1988) is a British-Iranian revolutionary, hacker, and programmer who is known for his leading role in the bitcoin project, and for pioneering many open source projects. Forbes listed Taaki in their top 30 entrepreneurs of 2014.. Taaki driven by the political philosophy of the Rojava revolution, travelled to Syria serving in the YPG military, and worked in Rojava's ... Wallet Commands Commands pertaining to bitcoin keys and payment addresses. Stealth Commands Commands pertaining to stealth payments and addresses. Transaction Commands Commands pertaining to manipulation of transactions, excluding network calls. Online Commands Commands that communicate on the bitcoin network. Hash Commands Satoshi Nakamoto and Martti Malmi. Bitcoin.org was originally registered and owned by Bitcoin's first two developers, Satoshi Nakamoto and Martti Malmi.When Nakamoto left the project, he gave ownership of the domain to additional people, separate from the Bitcoin developers, to spread responsibility and prevent any one person or group from easily gaining control over the Bitcoin project.
HOW TO GET A BITCOIN WALLET - Safe and Secure Way - YouTube
QUE BILLETERAS O WALLETS PARA CRIPTOMONEDAS SON LAS MEJORES? En este video compartimos las mejores wallets para bitcoin y otras criptomonedas, tanto wallets ... Sign in to like videos, comment, and subscribe. Sign in. Watch Queue Queue The second entry into my 'Using Crypto' series! LINKS: 1) https://www.torproject.org/download/ (Safety first!) 2) https://electrum.org/#home (Official Electr... SET UP YOUR COINBASE ACCOUNT: https://goo.gl/mWo1aM HOW TO EARN WITH CRYPTOCURRENCY: BEGINNER’S GUIDE https://goo.gl/nTDLgS ----- Today we’re talking about h... Best Bitcoin Wallet? This guide is about one of the safest hardware crypto wallet currently on the market that is not a Ledger wallet or Trezor wallet. BC Va...