Bitcoin Code Erfahrung Seriös & in Deutscher Sprache ...
c++ - How to understand Bitcoin source code - Bitcoin ...
Bitcoin download SourceForge.net
bitcoin🤡cash - Funny things that proponent of BitcoinCash (BCash) say
Funny things that proponent of BitcoinCash (BCash) say. When people spread FUD (lies) about SegWit or the original Bitcoin, then we post it here. We also welcome discussion - but do keep it logical and based on arguments like math, source-code. We do not like arguments like: - someone once said that SegWit is insecure; But I can not explain why exactly that would be. - someone said that XYZ is bad, here watch this 120 minute video, that is my argument
This timeline video shows how Martti Malmi ported the first Bitcoin sourcecode from SourceForge to github, how Satohi and him worked on it for about a year and then Gavin Andressen joined in. It's important to know the people that build most of Bitcoin.
Can you guys point me, where i can learn from the ground?
Proposal: Fully Decentralised Exchange Mechanism for All Cryptocurrencies and Fiat.
We are a UK based research group that operates across two separate companies based at a major UK university. We have created a design for a fully decentralised exchange mechanism able to facilitate secure exchanges between cryptocurrencies and also fiat. The design provides the following features:
A mechanism to create a decentralised cryptocurrency exchange.
An architecture resistant to distributed denial of service attack.
Resilience to double spending: parties can specify the number of confirmations they require during an exchange, if an attack occurs during this window the network will issue a 'refund' to both parties rendering the attack ineffective.
Fully decentralised history of trading data.
Fully decentralised history of bid/ask data.
Extensibility: cryptocurrencies can be added or removed from this new decentralised exchange without the need for a central authority.
Back-porting these capabilities into existing cryptocurrencies will create further decentralisation. Each cryptocurrency then provides a full set of features to enable this decentralised exchange mechanism: as long as any one cryptocurrency with this capability exists so does the decentralised exchange. The more cryptocurrencies with this capability exist the more robust the decentralised exchange becomes.
Ability to extend this decentralised exchange mechanism to allow cryptocurrencies to be exchanged for fiat currencies such as USD and EUR via the same API.
Improved cryptocurrency accessibility for everyday users with a large amount of functionality being provided in one combined wallet-exchange based client. This will allow anyone to exchange fiat and cryptocurrencies unrestricted from their desktop, phone or laptop.
We have taken this design and its development as far as we can without funding, so are seeking investment and donations directly from the Bitcoin community. We wish to develop the core parts of the system in-house and then release them for most of the development to then take place within/alongside the opensource community. We are keen to take this approach because:
We believe this approach will achieve a better segregation of modules and their contracts, using 'design by contract', if the initial design is in place before the opensource community starts working on it. We are all too keenly aware of the design overlap that can occur in the early stages of design if too many developers are involved resulting in artefacts such as API and feature bloat. We are totally behind opensource development but ask yourself which approach did Satoshi use?
We want to build some proprietary technology alongside the decentralised exchange mechanism to fund a new company that is able to fund its own activities without having any external dependencies. This will allow us to deliver a number of other technologies we have in the pipe related to cryptocurrencies. A lot of these are as interesting as this and we plan to release most of them completely opensource too.
If we don’t receive sufficient interest within a few months we will release this design into the public domain so that it can be freely developed by the opensource community with what help we can provide unfunded. We believe that a secure design can only be achieved through peer review, especially in the domain of cryptography. Therefore whether this design is developed initially in-house or entirely via the opensource community we consider that ultimately the opensource approach is the only viable option for a successful implementation: no part of this system can be centralised or propriety in any way. The two key architects of this design are senior technologists at their respective companies; the first partner's background is in architecting and delivery of ultra-secure military and government communications systems, the second has been architecting and building entire virtual economies since the 90s. If successful the new company we start will be totally separate entity to these. Between the two authors we have direct access to a development team of fourteen which we are keen to throw into this full time as soon as we are able to attract sufficient funding. We would like to share the designs we have created with a select group of serious individuals who are looking to donate or invest. If you are technical and looking to donate or invest please contact us at metalair.org with some background on yourself. For the benefit of the community we plan to make all our work related to the decentralised exchange mechanism freely available opensource: the idea would not work if any part of it were centralised. We are looking to achieve £200k GBP equivalent to cover all development costs, with the total delivery time estimated at around a year from start. The costs are commensurate with the level of work required for this proposal; this is not yet another rehash of the Bitcoin sourcecode, there are several completely new components we need to develop as well as extensible client software that needs to be created from scratch. If we achieve our funding goals and start development we will also be looking for technical collaborators. We are accepting both crypto and fiat. Please donate to the following addresses if you would like to fund this project:
Fiat: Please see metalair.org for details.
If you will be donating an amount at or over £1,000GBP equivalent please contact us as we would like to (optionally) add you to our notable donors' page. metalair.org/donors.php. We are taking investment offers at or above £25k GBP. For serious investors, after an initial introduction, we are more than happy to meet face to face and undergo due diligence to any level required: please see our Investor Relations metalair.org/investors.php page. Donations that fall short of our goal will be used for other research, much of which we plan to publish for free consumption by the community, most of it related to cryptocurrencies. If we do not receive sufficient interest within approximately two months we will release our designs into the public domain. Please see metalair.org for more details.
This is the most 2014 sentiment of the year.An Australian manufacturer and marketing artiste and a programmer in Portland, Ore. who accept in no way truly met obtain successfully combined the year's two greatest phenomena: Bitcoin, and doge. The fruit: Dogecoin. And people are as a matter of fact using it.If you're not friendly with the doge meme, it's hard to explain — you put straight of partake of to just catch a glimpse of it yourself. Basically, someone on the Internet began posting images of Facetious Sans thought bubbles in the imagined syntax of a devastatingly ingenious Shiba Inu dog. Variations on the meme look like this.There's no position to it; it's rightful unified of those Internet things. But people value it — you can regard some "orderly ones" here. Everywhere three weeks ago, Jackson Palmer, who before daylight works in Adobe's Sydney marketing department, and who'd been following developments in the cryptocurrency everybody, absentmindedly tweeted, "Investing in Dogecoin, easy on the eyes confident it's the next big thing."He got some replies encouraging him to pursue the tenet, and a week later bought the territory Dogecoin.com. Inevitably, it got picked up on reddit, a breeding ground of doge activity. Meanwhile in Portland, Billy Markus had been trying to program his own digital currency that would be attractive to to a broader demographic than the profiteers who've flooded into Bitcoin. But the discharge had gone nowhere. Then he stumbled across Dogecoin.com within a lifetime or two of the place going live."The prime dingus I said was, 'This is so funny.' Then I said, 'I should unprejudiced authorize this coin.'"He Tweeted at Palmer saying he wanted to die in on it, and ahead Palmer on a par responded, started reconfiguring Bitcoin's sourcecode, which is publicly to hand, to direct its user-facing elements into the doge meme.Later Palmer wrote dorsum behind, and the partnership was formed. A minute more than a week after Palmer's jokey tweet, Dogecoin was launched.Again it got picked up on reddit, and instantly exploded. It is already the 13th seventh-largest cryptocurrency, according to Coinmarketcap, with a market-place value (i.e. enumerate of extant Dogecoins X penalty of $0.00086) of $8 million. It now enjoys its own detailed blown ecosystem: in augmentation to the website, it has a dedicated blog and forum, and of passage a subreddit.How has it done this?At bottom completely something called "tipping."If you're a geek who "performs" a "acceptable deed" on the Internet, it's happen to garden mode for people to "warning" you in your digital currency of choice. Exchange for instance: that kid who held up up his Bitcoin wallet's QR-code during ESPN's College Gameday got tipped thousands of dollars by the Bitcoin community exchange for such a brilliant motion of insurgent marketing. But it's become a bit costly to tip in Bitcoin, so people be struck by turned to Dogecoin. However with respect to a week after launching, Dogecoin became the second-most-tipped currency, the matched set say. They're hoping Facebook whim assume a widget they've been working on that would budget friends to "lagniappe" each other with dogecoin.Still, what's so great less Dogecoin?Technically speaking, it's more of a differing on Litecoin, which runs on a cryptographic program called Scrypt. Like Litecoin, the time it takes to process a Dogecoin deal is much shorter than for Bitcoin. There are also varied more Dogecoins that liking come into entity — 100 billion versus 21 million.But it's the mores that's sprung up encompassing it that's absolutely driving it forward. Palmer says it comes down to having a soften barrier of entry after people who power be interested in cryptocurrencies but are turned slack close to either the quotation of or so-far dubious background that surrounds Bitcoin. "It's not enchanting itself as kidding aside, it's not being utilized via people worrying relating to whether they'll behoove fecund in," Palmer said. "It's something to share as far as something thanks or kudos."Markus says his wife, who at opening was turned off work at hand his consideration in Bitcoin, has started mining Dogecoin herself — something you can do with your basic computer, different from mining Bitcoin, which at the moment requires industrial-strength processors. The tandem say they procure no aim of competing with Bitcoin, and both are lull ardent believers in its quiescent to substitution online banking. "It's a revolutionary technology, yes revolutionist," Markus says. "And it works as a shop of value because it's deflationary, there desire be a cap [on Bitcoins created">. It's a moment ago highly untrustworthy, which makes it hard to put to use, to lavish and spread it."How can you tell the Dogecoin fact is not a joke? This morning, Bitcoin and most other altcoins are up about 20%.Dogecoin? Up 250% and counting.
KYC-Tezos wallets vulnerable to "blind sig" attack
Summary Most KYC-Tezos wallets we tested are vulnerable to a simple yet catastrophic attack that can lead to loss of all funds on wallet (blind signature vulnerability). These wallets connect to a server (the RPC node) but they do not build the raw tx like normal cryptocurrency wallets, nor do they check the binary provided by the RPC before signing it. Should the RPC get hacked (or turn malicious) it will provide clients a malicious tx to sign: with no way to parse the binary, the unsuspecting user will sign a tx which sends 100% of their funds to the attacker's address. (Update: since publishing this post some wallets have fixed the issue, see table below) Ledger Ledger users are not safe. This video shows how funds can be stolen from a Ledger device. Demo To demonstrate the vulnerability we also expose a malicious RPC to test your wallet against it (warning: funds could be lost). Vulnerable wallets
Can set custom RPC?
No (fixed in 0.7.0b+)
No (fixed in v137+)
No (fixed in 13.0.0)
No (fixed in 4.0.0+)
No (fixed in 4.0.0+)
No (fixed in v0.4.3+)
Why it matters Cryptocurrency wallets were meant to be trustless, but most KYC-Tezos wallets are not. When you're signing any tx with these wallets you're trusting the server (RPC) to send your money where you actually want it to go. Even if you trust the sourcecode of your wallet and are not using a web wallet, you're still vulnerable. The RPC you rely upon could turn malicious (e.g. be hacked) at any moment in time, with no way for you to detect it. How the attack works
RPC turns malicious (e.g. gets hacked)
Wallet securely connects to malicious RPC via HTTPS
Wallet provides JSON of tx to build
RPC provides malicious binary sending funds to attacker's address
Wallet blindly signs binary
RPC broadcasts tx: funds are now lost
In a variant of the attack, the unsuspecting user will set a malicious RPC as custom RPC in their wallet. There are multiple ways someone could be tricked to do that (see Electrum hack below). Causes More than wallet developers themselves, we deem KYC-Tezos developers inadequacy and lack of understanding of an adversarial environment as the culprit for this simple yet potentially catastrophic vulnerability. 1.Wrong design The RPC exposes a JSON API to build the tx, which is then provided to the client for signing, and returned to the RPC for broadcast. This is not how a blockchain wallet should work: txs should be built and signed locally, and only then pushed to a server. 2.OCaml binary with no serialization specs In the KYC-Tezos APIs there is no spec for the transaction binary format. tezos-data-encoding is the library responsible for encoding a tx, so the tx format is tightly coupled with the the serialization of OCaml objects. An OCaml binary with no spec is what led GUI wallet developers, who are not using OCaml, to just trust the binary provided by the RPC instead of parsing and checking it. A secure channel with your attacker SSL security between client and server won't help: if the RPC turns malicious, it will first establish a secure connection as usual and then provide a malicious tx to sign. Hiding in plain sight, KYC-Tezos APIs actually hint  to the vulnerability. The "solution" they suggest is securing the connection, which as already explained does not solve the issue at all while providing users a false sense of security. Hiding in plain sight: a hint from KYC-Tezos APIs What happened to Electrum Recently more than $750,000 were stolen by an attacker spawning malicious Electrum servers and stealing BTC from Electrum users.  The attack succeeded despite Electrum being way more secure than KYC-Tezos wallets: with Electrum the tx is generated by the client and not by the server. Malicious RPC demo Set this custom RPC in your wallet to test the vulnerability:
WARNING: IF YOUR WALLET IS VULNERABLE FUNDS WILL BE LOST AND SENT TO FOUNDATION BAKER 1 (tz3RDC3Jdn4j15J7bBHZd29EUee9gVB1CxD9) As safety measure this demo RPC only manipulates recpient's address, and not the transaction amount as well. If your wallet is vulnerable and not listed above yet, please let us know. How we fixed it We fixed the vulnerability in LibreBox by checking portions of the tx (such as destination address, amount, etc) after a reverse-engineering of the tx format itself. Suggested next steps
KYC-Tezos users: do not sign any tx with a vulnerable wallet until the vulnerability is addressed.
Wallet developers: immediately start warning your users of the danger, until binary txs are parsed and checked. If you resolved the issue or if your wallet is not listed, feel free to contact us to update this post.
Tezos Foundation: immediately release specs for the binary tx format, and improve documentation to a more decent standard.
Hi everyone, with recent talks about a possible 51% attack, I've set out on an adventure to see if I could possibly find forks in the blockchain. Exhibit A The first version of my little tool (written in C) basically treated the blk0001.dat file on disk like one big chain (hey, it's supposed to be the blockchain right?) but I learned that blocks may be downloaded and stored in the wrong order. So, I'd have to think of some data structure to make a huge graph out of all the blocks and then find the nodes which have the same parent. Binary Tree? Linked-list? Throw some bloomfilters in to the mix to keep things at a decent performance level? And all of it in C? There had to be an easier way! The first thing I tried, was a very naive attempt of simply letting a graphing software (graphviz) create a flowgraph of all the blocks (all 2.6 million of them(!)) which worked as well as you would've imagined: "Error: out of memory -- It did work to some extend (about 60k nodes) but not nearly enough to map out the whole blockchain. So I set out to use a different approach and found myself thinking "why not use my favorite software in the world: sqlite!" Sqlite is an amazing piece of technology, it's generally recognised to be very well written and very stable, and I've been using/abusing it for a few projects in the past which handle massive amounts of data. An hour plus a bit of hacky code later and I had a 1GB database containing the whole blockchain, which I could query and get results from within seconds! Let's see how many blocks have the same parent (identical prev_block hash): sqlite> SELECT id, timestamp, block_hash, parent_hash, count(parent_hash) c FROM blocks GROUP BY parent_hash HAVING c > 1;
and indeed if I look for one of the parent_hash values: sqlite> SELECT id, timestamp, block_hash, parent_hash FROM blocks WHERE parent_hash = "0e59cf4d13c4277befcb4c4b7ff41e4a3d8eaac1f25ceb58bc0609ba09089e0a";
we indeed see that there are two blocks that where solved within 4 seconds of each other with the same parent. This is called an orphan block: https://bitcoin.stackexchange.com/q/8172 Anyways, that's a quick first dive in to the blockchain and what secrets it may hold! :) I'll publish the sourcecode later (after cleaning it up a bit). Edit: Source code!
Hi Redditors. I am going to post in this thread my experiences in getting my Desktop (Debian) machine running Armory in watch-only mode, and coupling that with an offline Raspberry Pi (which holds my private keys) for signing the transactions previously made in watch-only mode. I actually compiled Armory from source directly on my Pi. This guide is probably more for the bitcoin 'power user', as to run Armory online, and broadcast the signed transactions, you need to have a bitcoin full node running (bitcoind). Basic requirements:
Online machine - running a full node (bitcoind)
Raspberry Pi - I used an old Pi 1 Model B with just 512Mb memory, and 2 USB slots.
2x USB thumb-drives. One for wallet backups, the other for transferring unsigned tx's to the rPi, and signed tx's back to the Desktop.
Armory 0.96.4 for the Raspberry Pi 1, Model B (512Mb RAM, 2xUSB) (compiled from github sourcecode on the Pi itself!)
Using the Pi as an offline complement to a Debian Desktop "watch-only" Armory install.
Desktop Debian Armory watch-only talks to my full node, bitcoind, which is also on the Debian desktop.
I'll post the guide in digestible sections...
I should begin by saying I installed source code from git, and got Armory to build the DB on my desktop initially, WITHOUT creating a wallet.. (This allowed me to debug what was going on a little!)
Go to Bitcoin.org, select Armory.. It leads to a Download from Git: https://github.com/goatpig/BitcoinArmory/releases Followed the procedure for Linux Debian verify code, compile, install, all straight-forward.. Began by running bitcoind, and telling Armory where to find it. This is the command I used, obviously it was all on one line and didn't include the arrows/explanations!:
python ArmoryQt.py \ --satoshi-datadir=/BlockChain/chain20180414/blocks \ # <-----(where my bitcoind blocks live) --datadir=/ArmoryDataDi \ # <-----(this is instead of ~/.armory) --dbdir=/ArmoryDataDidatabases # <-------(again, non std. place used for Armory's databases.. my choice.)
So, on the Desktop, after the initial "build databases" (NB the initial "Build Databases" took about 1.5h and my two CPUs were maxed the whole time, Temps up to 62C. Not ideal; Im not in a rush!) I then wanted to import a watch-only wallet. Before I did this, I took a full backup of the Armory data dir: /ArmoryDataDi (or ~/.armory in a default installation). I'd hate to have to make Armory do another full sync with the bitcoind node!
Next step: offline wallet (with Private Keys) is on a Raspberry Pi. I downloaded the source and managed to compile it on the pi itself! :) Though there were some gymnastics needed to setup the Pi. My Pi is running Raspbian based on Wheezy.. quite old! I did the following on the Pi:
apt-get update apt-get upgrade (<---took about an hour!) apt-get install autotools-dev apt-get install autoconf
Then I followed the instructions exactly as I had done for my Debian Desktop machine, EXCEPT: I had to increase the Pi's swap space. I upped it from 100Mb to 400Mb. The compilation took 7 hours, and my poor SD card got a thrashing. But after compilation, I put the Swap back to 100Mb and Armory runs ok with about 150Mb of memory (no swap needed). Swap increase on the Pi: use your favourite editor, and open the file /etc/dphys-swapfile add/change the following line:
Then, REBOOT the Pi:
sudo shutdown -h -P now
Once the compilation was done on the Pi, put the swap back, rebooted and created an Armory wallet. I added manual entropy and upped the encryption 'time' from 250ms to 2500ms - since the Pi is slow, but I'll be happy to wait for more iterations in the Key Derivation Function. Once the wallet was created, it obviously prompts you for backup. I want to add a private key of my own (i.e. import), so don't do the backup until this is over. I import my Private Key, and Armory checks that this corresponds to a Public Key, which I check is correct. This is the point now where the Pi storage medium (e.g an SD card) has to be properly destroyed if you ever get rid of it. I had thought that now would be a good time to decide if your new wallet will generate Segwit receiving addresses, and also addresses used to receive 'change' after a transaction.. But it seems Armory WON'T let you switch to P2SH-P2WPKH unless your Armory is connected to a node offering "WITNESS" service. Obviously, my Pi is offline and will never connect to a node, so the following will not work on the Pi:
x Use File Settings Fee and address types.
x Set the "Preferred Receive Address Type" to P2SH-P2WPKH
x Also Set the "Change Address" to P2SH-P2WPKH for left-over loose change!
NB: I thought about setting this on the Debian "watch-only" wallet, but that would surely mean doom, as the Pi would not know about those addresses and backups might not keep them.. who knows... So, end result:- no segwit for me just yet in my offline funds.
--If anyone can offer a solution to this, I'd be very grateful--
Ok, now this is a good point to back up your wallet on the Pi. It has your imported keys. I choose a Digital Backup - and put it on a USB key, which will never touch the internet and will be stored off-site. I also chose to encrypt it, because I'm good with passwords.. NB: The Armory paper backup will NOT back up your imported private keys, so keep those somewhere if you're not sweeping them. It would be prudent to have an Armory paper backup anyway, but remember it will likely NOT help you with that imported key. Now for the watch-only copy of the wallet. I want to get the "watch-only" version onto my Desktop Debian machine. On the Pi, I created (exported to a USB key) a "watching-only" copy of my wallet. I would use the RECOMMENDED approach, export the "Entire Wallet File". As you will see below, I initially exported only the ROOT data, which will NOT capture the watching-only part of the Private Key I entered manually above (i.e. the public Key!). Now, back on the Debian Desktop machine... I stopped all my crontab jobs; just give Armory uninterrupted CPU/memory/disk... I also stopped bitcoind and made a backup prior to any watch-only wallet being imported. I already made a backup of Armory on my Desktop, before any wallet import. (this was needed, as I made a mistake.. see below) So on the Debian Desktop machine, I begin by firing up bitcoind. my command for this is:
I know from bitter experience that doing a scan over the blockchain for a new wallet takes a looong time and a lot of CPU, and I'd like it to play nicely; not gobble all the memory and swap and run my 2xCPUs both at 100% for four hours... So... I aim to run with --ram-usage=X and --thread-count=X (For me in the end, X=1 but I began with X=4) I began with --ram-usage=4 (<--- = 4x128Mb) The result is below...
TypeError: cannot concatenate 'str' and 'int' objects
It didn't recognise the ram-usage and carried on, crippling my Debian desktop PC. This is where it gets dangerous; Armory can gobble so much memory and CPU that the windowing environment can cease up, and it can take over 30 minutes just to exit nicely from bitcoind and ArmoryDB. So, I ssh to the machine from another computer, and keep an eye on it with the command
I'd also be able to do a "sudo reboot now" if needed from here.
So, trying to get my --ram-usage command recognised, I tried this line (added quotes):
Loading Armory Engine: Armory Version: 0.96.4 Armory Build: None PyBtcWallet Version: 1.35 Detected Operating system: Linux OS Variant : ('debian', '9.4', '') User home-directory : /home/ Satoshi BTC directory : /BlockChain/chain20180414 Armory home dir : /ArmoryDataDi ArmoryDB directory : /ArmoryDataDidatabases Armory settings file : /ArmoryDataDiArmorySettings.txt Armory log file : /ArmoryDataDiarmorylog.txt Do wallet checking : True (ERROR) ArmoryUtils.py:3723 - Unsupported language specified. Defaulting to English (en) (ERROR) ArmoryQt.py:1833 - Failed to start Armory database: cannot concatenate 'str' and 'int' objects Traceback (most recent call last): File "ArmoryQt.py", line 1808, in startArmoryDBIfNecessary TheSDM.spawnDB(str(ARMORY_HOME_DIR), TheBDM.armoryDBDir) File "/BitcoinArmory/SDM.py", line 387, in spawnDB pargs.append('--ram-usage=' + ARMORY_RAM_USAGE) TypeError: cannot concatenate 'str' and 'int' objects
So, I edit the Armory python file SDM.py:
if ARMORY_RAM_USAGE != -1: pargs.append('--ram-usage=4') #COMMENTED THIS, SO I CAN HARDCODE =4 # ' + ARMORY_RAM_USAGE)
Running it, I now have acknowledgement of the --ram-usage=4:
(WARNING) SDM.py:400 - Spawning DB with command: /BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/BlockChain/chain20180414/blocks" --datadir="/ArmoryDataDi" --dbdir="/ArmoryDataDidatabases" --ram-usage=4
Also, even with ram-usage=4, it used too much memory, so I told it to quit. It took over 30 minutes to stop semi-nicely. The last thing it reported was:
ERROR - 00:25:21: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
But that didn't seem to matter or corrupt the Armory Database, so I think it's ok. So, I get brave and change SDM.py as below, and I make sure my script has a command line for --ram-usage="ABCDE" and --thread-count="FGHIJ"; the logic being that these strings "ABCDE" will pass the IF criteria below, and my hardcoded values will be used...
if ARMORY_RAM_USAGE != -1: pargs.append('--ram-usage=1') #COMMENTED THIS, SO I CAN HARDCODE =1 # ' + ARMORY_RAM_USAGE) if ARMORY_THREAD_COUNT != -1 pargs.append('--thread-count=1') #COMMENTED THIS, SO I CAN HARDCODE =1 #' + ARMORY_THREAD_COUNT)
So, as usual, I use my script and start this with: ./StartArm.sh (which uses command line:)
(this forces it to use my hard-coded values in SDM.py...) So, this is the command which it reports that it starts with:
(WARNING) SDM.py:400 - Spawning DB with command: /BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/BlockChain/chain20180414/blocks" --datadir="/ArmoryDataDi" --dbdir="/ArmoryDataDidatabases" --ram-usage=1 --thread-count=1
Again, this is where it gets dangerous; Armory can gobble so much memory and CPU that the windowing environment can cease up. So I ssh to the machine and keep an eye on it with:
So, on the Debian Desktop PC, I inserted the USB stick with the watch-only wallet I exported from the Pi. Start Armory... Import "Entire Wallet File" watch-only copy. Wait 4 hours.. YAY!!! After running Armory for about 30m, the memory usage dropped by 400m... wierd... It took ~2 hours to get 40% completion. After 3.5 hours it's almost there... The memory went up to about 1.7Gb in use and 900Mb of Swap, but the machine remained fairly responsive throughout, apart from a few (10?) periods at the start, where it appeared to freeze for 10-30s at a time. (That's where my ssh session came in handy - I could check the machine was still ok with a "free -h" command) Now, I can: Create an unsigned transaction on my Desktop, Save the tx to USB stick, Move to the Pi, Sign the tx, Move back to the Desktop, Broadcast the signed tx.
My initial Mistake: This caused me to have to roll-back my Armory database, using the backup. so you should try to avoid doing this.. On the Pi, I exported only the ROOT data, which will NOT capture the watching-only part of the Private Key It is RECOMMENDED to use the Digital Export of Entire Wallet File from the Pi when making a watch-only copy. If you just export just the "ROOT data", not the "Entire Wallet File", you'll have problems if you used an imported Private Key in the offline wallet, like I did. Using the ROOT data text import, after it finished... my balance was zero. So,. I tried a Help->Rescan Balance (Restart Armory, takes 1minute to get back up and running) No Luck. Still zero balance. So, I try Rescan Databases.. This will take longer. Nah.. no luck. So, I tried again, thinking it might be to do with the fact that I imported the text "root data" stuff, instead of following the (Recommended) export of watching-wallet file. So, I used my Armory backup, and wound back the ArmoryDataDi to the point before the install of the (zero balance) wallet. (you should not need to do this, as you will hopefully use the RECOMMENDED approach of exporting the "Entire Wallet File"!)
The Revelation of Satoshi Brothers! And yes, by “Brothers” I mean only chromosomal males - Satoshi’s Interstellar Comet will be a paradise with fully automated sexbots and will eliminate the need for feeeeeemales. In my most recent bout of huffing industrial solvents while staring at the blockchain sourcecode, the Great Satoshi came to me in a vision and revealed a new truth about His return. As we all know, Fiat will soon destroy the global economy. For eons dating back to 2009 we believed that superior Bitcoin would naturally take the place for all transactions. But Bitcoin is too great for this world. The governments and statist power brokers behind the scenes - powers like the People’s Republic of China, the United Nations, The Bilderbergs, Colonel Sanders, and Yum! Food Brands - will all conspire to bring the price of Bitcoin to zero on the day of judgement. The foolish among us will NOT HODL. But at the precise moment in which Bitcoin goes to zero - THAT is when Satoshi shall return on his interstellar comet. Where all is decided through smart contracts, where there is no fascist statist government, and no tyrannical age of consent laws to hold us back from experiencing unlimited euphoria. The original verses of the Bitcoin Blockchain Sacred Scrolls had been mistranslated. Bitcoin will not replace fiat. Bitcoin will TRANSCEND fiat by transcending the Earth itself. While the planet is consumed by nuclear fire, those of us with enough faith, autism, and a full spectrum cybersecurity background necessary to airgap protect our bitcoins to HODL at least one bitcoin at the moment of judgement will be transported instantaneously to the Interstellar Comet. Spread the gospel - no matter what the doomsayers say - HODL!!!
this information is the result by data-analysis from mailserver and sourcecode of crypterra.net (Oct 2017).
i will not answer any questions about how i broke into the system.
i will not share any sourcecode (clone preventing).
i'm in contact with EC3 (Europol ~ European Cybercrime Centre)
PLEASE NOTE:: I am keeping this here for safe keeping so sorry about the formatting. Not sure of the information. We should all continue to do indv research. I am filing reports and looking for stuff during my spare time.
So the bitcoin network starts off 2016 much stronger than it entered 2015. With over a billion $ in startup investment capital. It is crazy to realize that it is worth R111,415,577,100 in valuation (amount of coins multiplied by freemarket price) and this is just the beginning. Compare this to standard bank at R188,4B especially if you consider they are down about 40% in the past year where bitcoin is up 533% since 2013, and up 61% in the last 6 months. 1 bitcoin = R7404 Crazy you might say.. no. Go look up what quantitative easing is. Hint: The banks have been creating trillions, devaluing your savings. Bitcoin's processing power is now at 832,017,286,000,000,000 SHA256 hashes per second. This is what work it requires to mine bitcoin, what makes it secure and why we trust it more than some database in someone's vault that they can go edit if they please. This is real measurable energy consumption. Almost like digging up gold, just more humane. With 6 months left till the amount of new bitcoins mined halves to 12.5BTC per 10mins. We'll be entering the realm of sub 5% yearly monetary base inflation. This means instead of R788,400,000 worth of bitcoin created per month it will become only R394,200,000 worth per month newly issued. This new cycle will run for 4 years, like the last, before it halves again, and again. Until eventually in 140 years from now we have the last bit of bitcoin at 21million BTC. 21,000,000.000,000,000 should be enough for everyone. I've used rands so people can understand the scale of this thing a bit better. The exchange rates change over time according to free markets. Edit: I've added a list of links.. far from complete, but good enough to get started. I recommend south africans to use bitx market to exchange BTC/ZAR. Watch the links under knowledge in this list. Wallets: breadwallet iPhone bitcoin Android more on bitcoin.org/en/choose-your-wallet Exchanges: bitx ZAR, MYR, NGN, KES, IDR kraken EUR, USD, CAD, GBP, JPY, LTC okcoin CNY, USD vaultoro XAU (gold) There are many more.. Useful services for south african bitcoin holders: bitrefill Buy 8ta, cellc, mtn or vodacom airtime using bitcoin. takealot.com Buy things online for delivery, use instant eft then bitcoin on checkout. namecheap Domains for bitcoin. Tools: bitxZAR bitx market for south africans. bitcoinwisdom for seeing live exchange rates across many exchanges. cryptowatch has some other exchanges listed aswell and nice plotting tools. bitcointicker realtime market ticker. coinigy professional crypto trading platform (30 day free, 0.054BTC/mo) blockchain.info viewer, wallet provider and blockchain api blockr.io blockchain viewer and api bitpay easy bitcoin integration provider Community reddit/bitcoinreddit/btcbitcointalk forumsbitcoin.com forum
Looking for good documentation to start learning the technicalities of Bitcoin.
Hi all, I've just finished my exams (yay!) and so have a ton of free time to put to use. I do own some Bitcoin, and have a general understanding of how the network, wallets etc. work, but wish to actually gain a fairly significant technical understand of the Bitcoin network. So far I have on my reading list:
I was hoping you guys and girls could point out some good introductions / documentation on stuff like coloured coins, multisig transactions, SHA256 hashing and elliptical curve cryptography to add to my list? I've done some googling myself but was wondering if there's definitive info on these topics recommended by the community? I'm doing a physics/maths degree so anything with maths in is fine, but I have limited computer science knowledge sadly (hoping to improve on this)... So any reading recommendations??? Thanks in advanced. Edit: Thank you all for all the responses, it's much appreciated.. I've certainly got enough to get properly stuck into now :) Edit 2: Summarised for others: General:
I'm one of the main developers of LTCPP, and after several hard months, I've finally came to the decision to part with the main assets. LTCPP started in early 2012 as a project to fill the gap caused by a lack of a payment processor like BitPay for Litecoin. Due to developmental delays, and fragmentation of the team we fell behind. LTCPP has effectively disbanded, leaving me with all of the main assets, including the domain, emails, and code. Many of the main developers, as well as the manager of the project left the project early, effectively grinding LTCPP to a standstill. I currently have very little spare time to work on LTCPP, as well as to look for more developers/management, and because of this, LTCPP is going to be sold off. All assets will be sold as a bundle to the highest bidder, and the auction will be opened in the next few days on BitcoinTalk, payable in both Bitcoin and Litecoin. What's Included?
The LTCPP.NET domain name
The LTCPP.NET main email address adminatltcpp.net
All versions of the LTCPP sourcecode (we rewrote LTCPP at least 3 times, mostly because of "lead developers" leaving, and leftover devs abusing the chance to recode)
The LTCPP account on LitecoinTalk forum.litecoin.net
All prototype designs
The files will be delivered via a(n optionally GPG encrypted) tarball via your preferred method of file transfer. After personal information has been scrubbed from the Admin email for LTCPP, you will be provided with the credentials for the current email address, allowing you to reset the passwords of all LTCPP accounts to your preference. All communication can be delivered securely, encrypted with your GPG key on request. Over the next few days I will be preparing the assets to a reasonable state, and the auction will be live sometime next week. This reddit thread will be updated once the auction is up. Thanks, Someguy123 LTCPP Developer and Litecoin Forum administrator.
Is it possible for the owner of github.com to do this?
The owner of github.com will show you his version of Bitcoin Core source code and hashes, disguised as the real Bitcoin Core developers. Everything you see on github.com will look legit except that the sourcecode and hashes are altered.
How do we know what we see on github.com, when we go check out the files in the Bitcoin Core develpers' profiles, is actually real and not altered by the owner of github.com? Example, for the following files:
(I'm currently trying to verify the downloaded bitcoin-0.15.1-win64-setup.exe file by using the corresponding hash.) (Also trying to understand 'web of trust' and 'multiple signatures' thingy. It's not related to this post though.)
The Liquid proprietary sidechain from Blockstream has barely been discussed on /btc. Major Bitcoin companies like Bitfinex and BTCC will apparently use this blockchain to exchange value with each other. And apparently "many other financial players we’ve met with over the past several months" are excited too. Liquid is closed source. You cannot inspect it or modify it. Binary executables are not available, so you can't run it on your system. And in fact, you can't even use it. Any instances that are running are totally private. We know that Liquid is not secured by mining. It is a centralized system without proof-of-work whose blocks are signed by "functionaries". Or rather, Liquid is "decentralized, but in a different way ... Liquid trusts a majority of a small group of known blocksigners who rely on the system functioning". So yes, Liquid is centralized https://blockstream.com/2015/11/02/liquid-recap-and-faq/ Does Blockstream claim that ONLY value locked from the bitcoin mainnet will be represented on the mysterious Liquid sidechain? That Liquid currency units will not be created in any other way? If the answers to these questions are negative, Liquid is clearly an altcoin (OTOH why should anyone trust the answers anyway?) As well, if Liquid currency units are used in consumer accounts, they will not be interoperable with bitcoin. They would have to be exchanged. In the ridiculously brief discussion of Liquid on /Bitcoin, numerous red flags were raised with no answers offered by adam3us or austindhill, including
Liquid is "built from open source" only in the way that OSX is built from FreeBSD
Code for consensus, validation, in/out transfers is NOT AVAILABLE
What is the legal entity that will run Liquid? Will it have to comply with KYC/AML?
https://np.reddit.com/Bitcoin/comments/3osda3/liquid_sidechain_sourcecode/ If Blockstream wants to design a system that could serve consumers as a substitute for bitcoin, should they really be hosting conferences and signing documents whereby Bitcoin miners promise not to do anything that actually improves its scale? Should they really be labeling minor blocksize 75% consensus fork proposals as "altcoins"? Isn't that a wee bit hypocritical? Reddit shadowbanned the first account gillfranco which posted this earlier
Altcoin is a term that empowers bitcoin at the expense of other crypto-currencies. By using the altcoin term you are cognitively creating and enforcing the idea that the crypto-scene is dichotomised, with bitcoin on the one side and lumping all the other coins on the other. This generates subliminal bias toward bitcoin by singling it out as somehow special, thus magnifying the perception of its dominance relative to other coins. The net result is something of an endless causal nexus; bitcoin's power increases and we subconsciously conclude the dichotomy is therefore justified. Meanwhile of course, other coins struggle to compete in an environment that is neurolinguistically conditioned against them. Imagine if Lady Gaga had her own private category in record stores, whereas Katy Perry, Bruno Marrs and others simply got bundled into the only other category of that store: a section labelled "Other Artists". Aside from it being ridiculously unbalanced, the subconcious sense of 'difference' and publicity that Lady Gaga would consume from such an absurdity would be so astronomic that it would be enough to convince people that such a binary classification was necessary all along. Other artists, of course, would be in a state of permanent and suffocating subordination. Litecoin's evolution is reaching a crucial phase in respect of its relationship with the zeitgeist. If we are going to build on our successes we are going to have to break away from the developing cultural envelope that seeks to define us. We must start throwing some punches. One of the first punches is to collectively reject any suggestion that we are an altcoin. We must, wherever we have the opportunity, rewrite the narrative to consolidate and enforce ourselves as a living independent organism. This is not just to escape the perception that we are subordinate to bitcoin, but also to separate ourselves from the potentially infinite number of anonymous coins that we are being instructed to identify with.
Good day fellow crytocurrency playerz. Perhaps, like me, you have dedicated some think-time to the likely price movements of Bitcoin and altcoins (and in my case in particular privacy oriented coins) since Bitcoin has scaled with Segwit and a promise for 2X blocksizes that may or may not be fulfilled. If you follow my previous posts, you'll see that for a couple of months I was negative regarding the performance of a number of altcoins in the lead up to Bitcoin's Segwit scaling. If you can be bothered tracing back these posts, you'll see that I was heaviily criticised by the holders of these altcoins for which I predicted underperformance relative to Bitcoin. In the end, I was right that their particular altcoins would underperform Bitcoin, but that is besides the point. What I want to discuss now is the likely performance of Bitcoin, altcoins generally, and privacy altcoins in particular for the rest of 2017 now that Bitcoin has scaled with Segwit (and double blocksize is at least promised at this point). In particular, I want to discuss major altcoins Ether, Dash, and privacy oriented altcoins Monero, Zcash and ZenCash. Firstly, in the short term being the remainder of this year, I DO NOT expect Bitcoin to substantially outperform altcoins. I expect both Bitcoin and altcoins to rise in price substantially for the rest of 2017, but to do so to a roughly similar degree. While it is not my base case scenario, I think it is just as likely that altcoins as a whole will outperform Bitcoin as it is the other way around. Of the altcoins discussed in this post, I view Dash and ZenCash as being least vulnerable to downside risks. While my base case scenario is not for them to lose value over the remainder of the year, I see Ethereum, Zcash and Monero as each being vulnerable to foreseeable downside risks. Let me explain my reasoning, and please remember that for none of these coins am I predicting substantial price declines. Rather I'm offering suggestions as to their likely performance relative to each other and relative to the market. The "market" I refer to is straightforward - it is the cryptocurrency market as described and valued on coinmarketcap.com My personal belief is that Bitcoin will rise overall for the remainder of the year with more upside risk than downside risk. Recent events, for instance the Chinese ICO ban, or the as yet unconfirmed news of China banning Bitcoin exchanges reinforced this for me. Both items of news were very significant bad news (although the ban is unconfirmed), but all that could do was drop Bitcoin 20 per cent, and back it came roaring again recovering about 10 of that 20 per cent. Fundamentally I just see new money flowing into Bitcoin for the remainder of the year, and I expect it to soak up any bad news that emerges, and ultimately lead to a higher Bitcoin price. Ethereum I believe has both more upside and more downside potential than Bitcoin. Given how high risk and volatile a play the cryptocurrency market is, I personally don't see the benefit in choosing a higher risk asset within the space (Ethereum) over a lower risk asset within the space (Bitcoin) notwithstanding the lower risk asset has less upside potential as well as downside. I would not choose to hold Zcash or Monero at this stage. Zcash has underperformed Bitcoin even since July when Segwit 2X came into force. All the other altcoins I discuss in this post besides Zcash have gone up or pretty much sideways relative to Bitcoin since July. I think the market is less enthusiastic about Zcash than other coins at this point, and I think one of the reasons for this is that Zcash already rose so quickly this year, and I do not expect it to outperform for the rest of this year. With regards to Monero, despite having mined it significantly, I have always had great reservations about the coin, and always mined and sold. In fact one of the weaknesses I see in Monero in the short term is that I believe many miners have a similar lack of faith in the coin as I as a miner had. To me this both puts downward pressure on upward price swings, and tends to make Monero drop more sharply than the market as a whole when the market declines. My fundamental lack of faith in Monero though is my belief that it is simply not scaleable and therefore does not have the upside that other privacy coins that can be shown to scale could have. There were short term opportunities with Monero, like the recent 2x plus rise on the news Bithumb was listing Monero, but to my mind these are short term plays, and such trades tend not to fit with my investment style and model. Which brings me to Dash and ZenCash. While Dash is not per-se a privacy coin anymore, it has a privacy enhancing feature called DarkSend. I like the look of Dash for the remainder of this year. It is very well governed, and continues on with its Evolution upgrade to bring crypto to the masses. Of course, that may seem like a blue-sky dream, but Dash's governance structure has produced results with upgrade campaigns in the past, and I believe they're as or more equipped than any other development team to drink from the Holy Grail of mass adoption of cryptocurrency, so to speak. Dash's Masternode system locks a lot of supply into highly-invested masternode operators, and this tends to mean Dash often declines less rapidly than the market when the market has a very bad day. I do not own Dash at this point but I will be buying sometime before the end of October. Finally, the privacy oriented coin ZenCash makes a lot of sense to me when considering the balances of upside risk and downside risk. ZenCash derived much of its original sourcecode from Zcash, but it made changes, including a Secure Node system to further enhance privacy. As ZenCash's development rolls out, I see it having the a substantial possibility of outperforming the market for the rest of this year, in contrast to Zcash. This is because ZenCash is currently at a very low marketcap, roughly $17 million to Zcash's $475 million. If you compare Bitcoin Cash to Bitcoin, it has traded up and down, but Bitcoin Cash is somewhere around 13+ per cent of Bitcoin's value, you can see how low a multiple of ZenCash is trading relative to Zcash. I see ZenCash increasing its value as a percentage of Zcash's value this year. I see it equaling or outperforming the market as a whole. Upside risks are successful rollout of Secure Nodes, and if ZenCash can get included in a mobile multi-coin wallet like Coinomi or another. At the moment the only downside risk I see to ZenCash is general market risk, that is it will go down with the cryptocurrency market if the overall market goes down. Well, those were my six pence, and you can keep the change kind sirs (and ladies).
I just tried to use the source version and some Base58tools (https://github.com/matja/bitcoin-tool.git) to convert bitcoin keys to BitcoinNano. Converting the Base58check to nano prefix 0x8c / 140 to import it in the BitcoinNano daemon was easy. However it turns out the BitcoinNano sourcecode does not have any SegWit features, so you cant do a "addwitnessaddress". So no importing of BTN for SegWit keys possible... Do they only offer webwallet signup? Has anyone successfully claimed SegWit BitcoinNano via registration and message signing on btcnano.org ? note: See this thread: https://www.reddit.com/BitcoinAirdrops/comments/7s5pov/bitcoin_nano_claim_and_deposit_guide/
Bitcoin Core integration/staging tree. https://bitcoincore.org. What is Bitcoin? Bitcoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the ... Der Bitcoin Code erkennt in 0,01 Sekunden, wie sich der Kurs einer Kryptowährung verändern wird. Zeitgleich mit dieser Erkenntnis reagiert der Bot und kauft oder verkauft die jeweilige Position. Die Genauigkeit ist dabei sehr hoch, was die Gewinnwahrscheinlichkeit rasant steigen lässt. Nach unseren Erfahrungen mit dieser Plattform können wir sagen, dass der Bot tatsächlich zu ... Bitcoin uses peer-to-peer technology to operate with no central authority or banks; managing transactions and the issuing of bitcoins is carried out collectively by the network. Bitcoin is open-source; its design is public, nobody owns or controls Bitcoin and everyone can take part. Through many of its unique properties, Bitcoin allows exciting ... Bitcoin Core is a community-driven free software project, released under the MIT license. Verify release signatures Download torrent Source code Show version history. Bitcoin Core Release Signing Keys v0.8.6 - 0.9.2.1 v0.9.3 - 0.10.2 v0.11.0+ Or choose your operating system. Windows exe - zip. Mac OS X dmg - tar.gz. Linux (tgz) 64 bit. ARM Linux 64 bit - 32 bit. Linux (Snap Store) Support ... Bitcoin Core integration/staging tree c-plus-plus cryptography bitcoin p2p cryptocurrency C++ MIT 26,499 45,612 573 (40 issues need help) 395 Updated Oct 25, 2020
Building Bitcoin Software From Source Code - YouTube
This short video shows how to compile the bitcoin source code on linux (ubunu). an easy task to do but it take some time (around 15 min) please read the instruction in the official github https ... The Bitcoin Source Code: A Guided Tour - Part 2: Genesis Block and nSubsidy Halving Interval - Duration: 9:14. Oscar Chambers 1,323 views. 9:14. Presentation Slides: http://averageradical.github.io/compile/#/ Send Tips directly to KevG @ bitcoin:1QDEf7xr33aHGPZUHg9WHQkyGLcYKXcv4i Much of the software ... The Bitcoin Source Code: A Guided Tour - Part 4: Splitting the Mining Reward - Duration: 16:39. Oscar Chambers 595 views. 16:39. Bitcoin/Altcoin Developer Guide - 5 - Scripting Language, Block ... The Bitcoin Source Code: A Guided Tour - Part 3: Changing Max Supply and Coinbase Maturity - Duration: 9:43. Oscar Chambers 1,005 views. 9:43.