GitHub - bitcoin-abe/bitcoin-abe: Abe: block browser for

Myriad - A coin for everyone.

Myriad (XMY) is a Multi-PoW consensus protocol secured by 5 mining algorithms. Each one suits different hardware.
[link]

NobleCoin

A crypto currency for the most Noble.
[link]

I am a CTO of a "blockchain technology" startup, AMA

I've seen a lot of confusion regarding 'private blockchains' (aka permissioned ledgers, distributed ledger technology, ...) lately, and I think I'm in a good position to clarify what this technology is about, and what does it mean for Bitcoin.
First I'd like to introduce myself via facts of biography and projects I've been involved in:
Through the years I mostly worked with the Bitcoin blockchain, but I also researched private blockchains and talked with potential customers who might want to use a private blockchain or something like that.
So I'd like to address some common questions and misconceptions I've seen on /bitcoin.
Rhetoric question: Isn't a private blockchain just a database? Can't banks just use SQL as usual?
Answer: It certainly can be classified as a database, of a special kind. The Bitcoin blockchain is actually also a database of a special kind. They can certainly use SQL, but SQL, by itself, doesn't provide means of sharing a database between multiple parties in a secure way.
Use of SQL and use of blockchains isn't mutually exclusive. SQL is being used by a number of Bitcoin projects, for example: blockchain.info, Coinbase's Toshi, Abe block explorer, and Chromanode. There is at least one Bitcoin full node implementation which uses SQL: bits of proof supernode.
Question: Can't banks just use a distributed database or a shared ledger?
Answer: Modern distributed databases are designed with an assumption that all computers in a cluster are trusted. If an attacker can hijack a single computer of a cluster, he can compromise the whole clustedatabase.
Thus this software products aren't suitable for a case when a database needs to be shared between multiple parties which do not unconditionally trust each other. E.g. suppose banks A, B, C decided to share some database between themselves. If C's IT team fucks up, whole database might get corrupt.
Byzantine fault tolerance is an old concept, but it's rarely used in enterprise software. So there are no secure shared database products banks could use.
Bitcoin sparked new interest in secure distributed technology by demonstrating that it's actually possible & feasible. Now banks want it. Products which are inspired by Bitcoin and its block chain approach, and so they are often called "blockchains".
Misconception: A blockchain without proof-of-work makes no sense.
Answer: It was demonstrated that proof-of-stake can be quite good, both in theory and in practice. PoW and PoS have different security characteristics, which one is better is a matter of an opinion.
Other BFT consensus algorithms can be combined with a blockchain approach, e.g. Ripple/Stellar consensus, or PBFT-style three phase commit. They have well-understood security properties which differ from PoW and PoS.
In my opinion, if something has a chain of blocks, it can be called a blockchain. But if you want to understand a blockchain in a very narrow sense I don't mind, there are other terms like 'distributed ledger' which can be used instead.
Misconception: Banks use permissioned ledgers to implement "bankcoins", which are going to fail.
Answer: As someone who talked with many people from many banks, I can tell you they have very little interest for 'bankcoins', i.e. things which resemble Bitcoin. They might experiment with things like that just for shits and giggles, but there are no plans to launch it for real.
Banks plan to use permissioned ledger either to improve processes which are currently inefficient or non-secure; or to enable new business models.
Misconception: Banks should just use Bitcoin instead of this permissioned ledger mumbo-jumbo.
Answer: Bitcoin isn't suitable for things which permissioned ledgers aim to solve. It's, like, not related.
It would certainly be nice if banks provided Bitcoin services, but for them it's too much PITA with little to no benefits, as Bitcoin market is too small. Privatbank in Ukraine provides a Bitcoin payment service to merchant, kinda like Coinbase. So it's possible, just not common now.
So I think that Bitcoin can peacefully co-exist with private/permissioned blockchain/ledger technology: they aim to solve different problems, in different ways. There is some risk of a "bankcoin" competing with Bitcoin in future, but it's very small.
On contrary, I think adoption of crypto-based tech by banks is actually good for Bitcoin, as e.g. irreversible crypto money can be used for secure fiat <-> Bitcoin exchanges, which is good for Bitcoin, as it might reduce a hassle of buying Bitcoin, and thus increase userbase. Devices used to keep crypto bank money might also be used as secure Bitcoin wallets, etc.
I'll be happy to answer questions related to projects I've been involved in or blockchains in general.
submitted by killerstorm to Bitcoin [link] [comments]

Trying to get ABE working with Dogecoin. [20,000 DOGE Bounty]

I have been trying to get dogecoin set up on ABE: https://github.com/bitcoin-abe/bitcoin-abe
Does anyone have any experience in setting this up? Here is the error that I am getting:
Skipped 96 bytes at block end block_tx 1180 1 Skipped 96 bytes at block end block_tx 1181 1 Skipped 95 bytes at block end Exception at 235523 Failed to catch up {'blkfile_number': 100000, 'dirname': u'/home/ubuntu/.dogecoin', 'chain_id': 8, 'id': 1, 'blkfile_offset': 208572} Traceback (most recent call last): File "/uslocal/lib/python2.7/dist-packages/Abe/DataStore.py", line 2422, in catch_up store.catch_up_dir(dircfg) File "/uslocal/lib/python2.7/dist-packages/Abe/DataStore.py", line 2475, in catch_up_dir store.import_blkdat(dircfg, ds, filename[0]) File "/uslocal/lib/python2.7/dist-packages/Abe/DataStore.py", line 2596, in import_blkdat b = store.parse_block(ds, chain_id, magic, length) File "/uslocal/lib/python2.7/dist-packages/Abe/DataStore.py", line 2630, in parse_block d['transactions'].append(deserialize.parse_Transaction(ds)) File "/uslocal/lib/python2.7/dist-packages/Abe/deserialize.py", line 90, in parse_Transaction for i in xrange(n_vout): OverflowError: Python int too large to convert to C long
I am willing to tip 20,000 Doge to whoever knows how I can get this working. I have not had any problems setting up ABE with any other coins.
submitted by jeffmthomas to dogecoin [link] [comments]

way to explore blockchain offline?

with the blockchain hosted on a computer's hard drive, is it possible to explore the blockchain while offline? i imagine it wouldn't be too hard to write a program that could represent the data in a gui. does something like this exist already?
submitted by chabes to Bitcoin [link] [comments]

[HIRING] Blockchain hacker/smart person -> I want to know how to parse data from the block chain

thats about what I know right now.. I am looking for someone to teach me how to gather data from the blockchain, examine transactions, identify used addresses... etc for some data analysis i like to do.
I am somewhat technically literate... you should be to.
submitted by I__Know__Things to Jobs4Bitcoins [link] [comments]

Litecoin - Abe

Hi there
Is there someone who successfully run litecoin on bitcoin abe / abe. I used this as my chain config.
CHAIN_CONFIG = [{"chain":"Litecoin", "code3":"LTC", "address_version":"0x30", "magic":"\xfb\xc0\xb6\xdb"}]
But im getting this error:
Opened /home/ubuntu/.litecoin/blocks/blk00046.dat
Exception at 3652130237
Failed to catch up {'blkfile_offset': 29167380, 'blkfile_number': 100046, 'chain_id': 1, 'loader': None, 'conf': u'/home/ubuntu/.litecoin/litecoin.conf', 'dirname': '/home/ubuntu/.litecoin', 'id': Decimal('439')}
Traceback (most recent call last):
>! File "Abe/DataStore.py", line 2530, in catch_up!<
store.catch_up_dir(dircfg)
>! File "Abe/DataStore.py", line 2828, in catch_up_dir!<
store.import_blkdat(dircfg, ds, blkfile['name'])
>! File "Abe/DataStore.py", line 2950, in import_blkdat!<
b = chain.ds_parse_block(ds)
>! File "Abe/Chain/__init__.py", line 82, in ds_parse_block!<
d['transactions'].append(chain.ds_parse_transaction(ds))
>! File "Abe/Chain/__init__.py", line 75, in ds_parse_transaction!<
return deserialize.parse_Transaction(ds)
>! File "Abe/deserialize.py", line 90, in parse_Transaction!<
d['txIn'].append(parse_TxIn(vds))
>! File "Abe/deserialize.py", line 46, in parse_TxIn!<
d['sequence'] = vds.read_uint32()
>! File "Abe/BCDataStream.py", line 71, in read_uint32!<
def read_uint32 (self): return self._read_num('
>! File "Abe/BCDataStream.py", line 110, in _read_num!<
(i,) = struct.unpack_from(format, self.input, self.read_cursor)
error: unpack_from requires a buffer of at least 4 bytes
submitted by mjbquieta to litecoin [link] [comments]

Recent blockchain SQL dumps

Are there any recent blockchain SQL database dumps anywhere to be found? In the past http://dumps.webbtc.com/bitcoin/ has been a valid source, but it seems to be down for quite a while now. Using tools like Bitcoin-Abe to parse the blockchain and write it into a DB don't seem to be feasible anymore (seeing this issue here https://github.com/bitcoin-abe/bitcoin-abe/issues/207).
I'd like to have such a dump because I figured that analysis regarding user clustering, unspent outputs and balances are best done with a DB. Walking over the locally stored dat files seems to be unfeasible without absurdly powerful hardware.
submitted by Izzy102 to Bitcoin [link] [comments]

How to store the blockchain in a MYSQL database?

I've seen Abe, but it takes forever to sync to the blockchain (and I also think there's some kind of bug that prevents it from resuming if it gets interrupted.)
I've also found Bitcoin_Updater but it's 6 years old and I don't know how to get it up and running (https://github.com/thallium205/Bitcoin_Updater )
Anyone have any other suggestions? I like the simplicity of the schema of Bitcoin_Updater.
(Please don't tell me that there's not a good reason to do this-- I"m doing it as part of a learning assignment)
submitted by sundance1555 to Bitcoin [link] [comments]

SPECIAL HTMLCOIN WORLD MEETING JUNE 17, 2017.

[b]TOPIC:[/b] SPECIAL HTMLCOIN WORLD MEETING JUNE 17, 2017.
[b]AGENDA:[/b] TO DECIDE THE DETAILS OF THE WALLET UPDATE AND RELATED MATTERS.
[b]TIME:[/b] JUNE 17, 2017, AT 10:30 AM BRITISH SUMMER TIME (BST).
[b]PARTICIPANTS:[/b] ATTENDED BY 27 INDEPENDENT DEVELOPERS AND COMMUNITY MEMBERS.
[b]COUNTRY OF ORIGIN:[/b] THE UNITED STATES OF AMERICA, THE UNITED KINGDOM OF GREAT BRITAIN AND NORTHERN IRELAND, THE REPUBLIC OF THE PHILIPPINES, THE PEOPLE'S REPUBLIC OF BANGLADESH, THE FEDERATIVE REPUBLIC OF BRAZIL, THE ISLAMIC REPUBLIC OF PAKISTAN, THE REPUBLIC OF SINGAPORE, ROMANIA, THE FRENCH REPUBLIC, THE UNITED ARAB EMIRATES (DUBAI), THE REPUBLIC OF COLOMBIA, THE UNITED MEXICAN STATES, THE REPUBLIC OF INDONESIA, THE SOCIALIST REPUBLIC OF VIETNAM, THE REPUBLIC OF INDIA, THE REPUBLIC OF BULGARIA, AND THE RUSSIAN FEDERATION.
[b]WE AGREED ON THE FOLLOWING:[/b]
[b]ABSTRACT[/b]
[b]• We decided that Blockchain will not be reversed as requested by Bleutrade but we offer a possible solution. • We invited a Cryptocurrency Expert and a Computer Science faculty to help us understand the technical problem. • We are implementing checkpointing for Htmlcoin to hinder and stop hacking risk and future attacks. • We are releasing an updated wallet. • We want to understand more about the Bleutrade Insolvency Enigma. • Summary of the meeting and Implications of our decision as a community.[/b]
[b]DETAILS[/b]
[b]1. We, HTMLCOIN Developers and Community Members in attendance, decided that Blockchain will not be reversed from April 25, 2017, until the present date of this meeting.[/b] 1.1. The request of Bleutrade to reverse the blockchain was not granted by the core team. However, we offer them a possible solution for their claim of insolvency of 5.6 Billion by swapping the claimed lost coin to a new coin. It is important to note that not all of their holdings are lost, if any. We are waiting for their response on this offer. See section 5 - 5.5 for more information about Bleutrade Insolvency Enigma. [b]1.2. We are looking forward to resolving this issue of insolvency claim with Bleutrade because we were part of this exchange since their early days in 2014, Bleutrade is a family to us[/b]. 1.3. We believe that reversing will do more harm than good. If the blockchain will be reversed, it will erase all 1 month worth of transaction, that would be a bigger disaster. 1.4. If we reverse the blockchain this would mean that all transactions conducted from April 25, 2017, to date will be nullified, all transactions thereafter will turn to zero. Reversing the wallet is NOT an option.
[b]2. We invited a cryptocurrency expert, Peter Bushnell, a former constituent of The University of Oxford, and Zac Smith, a faculty of Computer Science of New Mexico University, to help us understand the extent of our coin’s technical problem.[/b] 2.1. Peter Bushnell’s advised that checkpointing be added in the coin and that the blockchain should not be reversed. Zac Smith agreed on these recommendations as well. The two experts are instrumental in our present decision for the coin, moving forward.
[b]3. We are implementing checkpointing for Htmlcoin, as the new feature of the wallet to hinder and stop hacking risk and future attacks.[/b] 3.1. Simply put, the checkpoint prevents attackers from replacing the existing chain with a different chain to protects against transaction reversal. Checkpoints are built into the Bitcoin code, they are defined as a block height and its hash, the Bitcoin software will only connect to chains with those checkpoints in. 3.2. Automatic Checkpointing is real time checkpointing, rather than define them in the code they are broadcast from a node on the network. In the source code there will be a public key, only a node with a corresponding private key can send out checkpoints, that node will also need to configure a depth for the checkpoints, that is how many blocks there needs to be after a block before it is checkpointed, so a depth of 5 means that a block will be checkpointed when there are 4 confirmations for it making it 5 blocks deep from the top of the chain.
[b]4. We are releasing a new Wallets and Files.[/b] 4.1. This is the location of the Windows Wallet: http://seed.htmlcoin.net/HTMLCoin-1.3.2.1-setup.exe 4.2 This is the location of the Mac Wallet: http://seed.htmlcoin.net/Htmlcoin-1.3.2.1-Mac.dmg 4.3 This is the Blockchain: http://seed.htmlcoin.net/htmlcoin_blockchain.zip 4.4. This is our GitHub account: https://github.com/HTMLCOIN/HTML5
[b]5. The Bleutrade Insolvency Enigma.[/b] 5.1. The Attacker Deposited 5.7 Billion to Bleutrade and Withdraw the coin. 5.2. Bleutrade informed us that “The attacker DEPOSITED 5.6 Billion in Bleutrade, sold an amount to Doge and withdraw the remainder.” 5.3. HTMLCOIN Team investigated and found out that the total amount stolen from the attacker in Bleutrade is 928440.36517198 DOGE. See the spreadsheet, https://docs.google.com/spreadsheets/d/1FOJC3ayvP2gV69QfddmLPuVb06OAqw2mWfoVVT02Hww/edit#gid=0 5.4. Logic will dictate that the insolvency in Bleutrade should only be 928440.36517198 DOGE, not the 5.6 Billion HTMLCOINS as claimed by Bleutrade. 5.5. Because of this Enigmatic Insolvency claim by Bleutrade, we are asking them to clarify why there is such a huge insolvency, given that the attacker deposited the amount of 5.6 Billion to Bleutrade, meaning Bleutrade do not own the 5.6 Billion HTMLCOIN in the first place. The 5.6 Billion is owned by the attacker. 5.6. On June 8, 2017, Bleutrade informed us the GOOD NEWS that the attacker was denied by the network. 5.6.1. Below are the 2 deposits deleted from the blockchain even after several confirmations: 5.6.1.1. HTML5 c8d657812abc1779d924235e6938a5c35e7428f5916eec38c64ea34ec18217f2 4605383 2017-04-25 23:09:17 HRYCxScEBr8R4eLRc9zwsmU8jX8gvcoM6a 2947478457.86640000 5.6.1.2. HTML5 9699446ff34e6224a177df2566c6503f791330256601c7126ad10ed225c61b3b 4604813 2017-04-25 16:16:14 HTENYcoKi3NYM13AhwrjzsEN9AGnVYYYui 2852036157.86640000 5.6.1.3. Total: 5799514615.73279954 HTML5 5.7. Activity and Identity of the Hacker.
[b]Username yanmar E-mail [email protected][/b] ::: LOGIN 2017-04-25 16:06:56.578353+00 ::: --- IP 146.185.31.214 ::: --- LAST ACTIVITY 2017-04-26 00:49:30.656994+00 ::: --- TIMEZONE -3 ::: --- BROWSER Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36 ::: --- LANGS en-US,en;q=0.8 ::: LOGIN 2017-04-25 12:14:44.607931+00 ::: --- IP 37.130.229.149 ::: --- LAST ACTIVITY 2017-04-25 15:40:26.436481+00 ::: --- TIMEZONE -3 ::: --- BROWSER Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36 ::: --- LANGS en-US,en;q=0.8
Withdraws to: HKW9SyBMMqmvqtFVt62M38p1DB3E7fPtN6 H8gG3N12VBxkTGXvVNnU8h14ZvivYDVSVs HMQ85E73ckbVX5km3531HfMk4Kn8egmmpV H9fcC7c4UpjABeAGKpaac1KFehjz6Ft5aX HJ6AeP636JQMt8HqtaDvUYggupZ7U3uh5t HUBWDWrMvxAwtAbKB48RAVrCZgwnqqbk51 HFncs5hxUFvxnieNqWC48xrVjYtTijb7Jj HQmwFURL5Rkb43gRNitKd5RfW4zZ2NNMcC
5.8. We understand that this is a challenge for both Bleutrade and HTMLCOIN Community. Because of this, we are here to cooperate with Bleutrade in resolving this enigma. We maintain open communication with Bleutrade.
[b]6. Summary of the meeting and Implications of our decision as a community.[/b] 6.1. Reversing the blockchain will do more harm than good. 6.2. Because we decided not to rollback the blockchain, all coins outside of Bleutrade, specifically in Yo Bit and Coin Gather, it will not turn to zero, they are legitimate. 6.3. We have instructed Yo Bit and Coin Gather to resume trading. 6.4. We are releasing an updated Windows Wallet, Mac Wallet, Blockchain File, and the HTMLCOIN account in GitHub. 6.5. We understand that the Attacker Deposited 5.7 Billion to Bleutrade. 6.6. That the attacker was denied by the network. 6.7. That the 2 deposits were deleted from the Blockchain. 6.8. That we need to understand more about the Bleutrades Insolvency Enigma and we are willing to cooperate in solving this issue. 6.9. The attack that happened in Bleutrade is not an isolated case to HTMLCOIN. Other cryptocurrencies in Bleutrade were also a victim of a similar attack, such as Virtacoin, Ambercoin, et cetera. 6.10. That we have the identity of the hacker. 6.11. We are maintaining open communication to Bleutrade to explore possible solutions. 6.12. Given with this experience, we are now implementing real-time checkpointing moving forward so that the will withstand possible attacks a feature that will make HTMLCOIN stronger in the future ahead.
SOURCE: https://docs.google.com/document/d/1JpkQpDVzDeU2C2tgwSh7I31VBEuy4eXiFY2kR36KFiM/edit?usp=sharing
submitted by HTMLCOIN to htmlcoin_community [link] [comments]

5 Fun things and useful services you can contribute to the network if you run your own full node!

Our active node count just above 500 nodes, which while the 4th most nodes for a crypto (behind bit, dash and lite) still seems pretty low given the size of our community. So I thought I'd make this little post to show some cool things to do with a node rather than just leave it sitting there running.
A note about security - you are broadcasting your IP to the entire cryptocurrency world when you run a node. It is essential that you run on an uncompromised computer kept free of malware, keyloggers and viruses. It is essential that you encrypt your wallet.dat with a very strong password (>16 chars, numbers and symbols). I would recommend not keeping too much in your wallet, keep most of it stored securely in an offline address.
submitted by peoplma to dogecoin [link] [comments]

SPECIAL HTMLCOIN WORLD MEETING JUNE 17, 2017.

TOPIC: SPECIAL HTMLCOIN WORLD MEETING JUNE 17, 2017.
AGENDA: TO DECIDE THE DETAILS OF THE WALLET UPDATE AND RELATED MATTERS.
TIME: JUNE 17, 2017, AT 10:30 AM BRITISH SUMMER TIME (BST).
PARTICIPANTS:] ATTENDED BY 27 INDEPENDENT DEVELOPERS AND COMMUNITY MEMBERS.
COUNTRY OF ORIGIN: THE UNITED STATES OF AMERICA, THE UNITED KINGDOM OF GREAT BRITAIN AND NORTHERN IRELAND, THE REPUBLIC OF THE PHILIPPINES, THE PEOPLE'S REPUBLIC OF BANGLADESH, THE FEDERATIVE REPUBLIC OF BRAZIL, THE ISLAMIC REPUBLIC OF PAKISTAN, THE REPUBLIC OF SINGAPORE, ROMANIA, THE FRENCH REPUBLIC, THE UNITED ARAB EMIRATES (DUBAI), THE REPUBLIC OF COLOMBIA, THE UNITED MEXICAN STATES, THE REPUBLIC OF INDONESIA, THE SOCIALIST REPUBLIC OF VIETNAM, THE REPUBLIC OF INDIA, THE REPUBLIC OF BULGARIA, AND THE RUSSIAN FEDERATION.
WE AGREED ON THE FOLLOWING:
ABSTRACT
• We decided that Blockchain will not be reversed as requested by Bleutrade but we offer a possible solution. • We invited a Cryptocurrency Expert and a Computer Science faculty to help us understand the technical problem. • We are implementing checkpointing for Htmlcoin to hinder and stop hacking risk and future attacks. • We are releasing an updated wallet. • We want to understand more about the Bleutrade Insolvency Enigma. • Summary of the meeting and Implications of our decision as a community.
DETAILS
  1. We, HTMLCOIN Developers and Community Members in attendance, decided that Blockchain will not be reversed from April 25, 2017, until the present date of this meeting.[/b] 1.1. The request of Bleutrade to reverse the blockchain was not granted by the core team. However, we offer them a possible solution for their claim of insolvency of 5.6 Billion by swapping the claimed lost coin to a new coin. It is important to note that not all of their holdings are lost, if any. We are waiting for their response on this offer. See section 5 - 5.5 for more information about Bleutrade Insolvency Enigma. 1.2. We are looking forward to resolving this issue of insolvency claim with Bleutrade because we were part of this exchange since their early days in 2014, Bleutrade is a family to us. 1.3. We believe that reversing will do more harm than good. If the blockchain will be reversed, it will erase all 1 month worth of transaction, that would be a bigger disaster. 1.4. If we reverse the blockchain this would mean that all transactions conducted from April 25, 2017, to date will be nullified, all transactions thereafter will turn to zero. Reversing the wallet is NOT an option.
  2. We invited a cryptocurrency expert, Peter Bushnell, a former constituent of The University of Oxford, and Zac Smith, a faculty of Computer Science of New Mexico University, to help us understand the extent of our coin’s technical problem. 2.1. Peter Bushnell’s advised that checkpointing be added in the coin and that the blockchain should not be reversed. Zac Smith agreed on these recommendations as well. The two experts are instrumental in our present decision for the coin, moving forward.
  3. We are implementing checkpointing for Htmlcoin, as the new feature of the wallet to hinder and stop hacking risk and future attacks. 3.1. Simply put, the checkpoint prevents attackers from replacing the existing chain with a different chain to protects against transaction reversal. Checkpoints are built into the Bitcoin code, they are defined as a block height and its hash, the Bitcoin software will only connect to chains with those checkpoints in. 3.2. Automatic Checkpointing is real time checkpointing, rather than define them in the code they are broadcast from a node on the network. In the source code there will be a public key, only a node with a corresponding private key can send out checkpoints, that node will also need to configure a depth for the checkpoints, that is how many blocks there needs to be after a block before it is checkpointed, so a depth of 5 means that a block will be checkpointed when there are 4 confirmations for it making it 5 blocks deep from the top of the chain.
  4. We are releasing a new Wallets and Files. 4.1. This is the location of the Windows Wallet: http://seed.htmlcoin.net/HTMLCoin-1.3.2.1-setup.exe 4.2 This is the location of the Mac Wallet: http://seed.htmlcoin.net/Htmlcoin-1.3.2.1-Mac.dmg 4.3 This is the Blockchain: http://seed.htmlcoin.net/htmlcoin_blockchain.zip 4.4. This is our GitHub account: https://github.com/HTMLCOIN/HTML5
  5. The Bleutrade Insolvency Enigma. 5.1. The Attacker Deposited 5.7 Billion to Bleutrade and Withdraw the coin. 5.2. Bleutrade informed us that “The attacker DEPOSITED 5.6 Billion in Bleutrade, sold an amount to Doge and withdraw the remainder.” 5.3. HTMLCOIN Team investigated and found out that the total amount stolen from the attacker in Bleutrade is 928440.36517198 DOGE. See the spreadsheet, https://docs.google.com/spreadsheets/d/1FOJC3ayvP2gV69QfddmLPuVb06OAqw2mWfoVVT02Hww/edit#gid=0 5.4. Logic will dictate that the insolvency in Bleutrade should only be 928440.36517198 DOGE, not the 5.6 Billion HTMLCOINS as claimed by Bleutrade. 5.5. Because of this Enigmatic Insolvency claim by Bleutrade, we are asking them to clarify why there is such a huge insolvency, given that the attacker deposited the amount of 5.6 Billion to Bleutrade, meaning Bleutrade do not own the 5.6 Billion HTMLCOIN in the first place. The 5.6 Billion is owned by the attacker. 5.6. On June 8, 2017, Bleutrade informed us the GOOD NEWS that the attacker was denied by the network. 5.6.1. Below are the 2 deposits deleted from the blockchain even after several confirmations: 5.6.1.1. HTML5 c8d657812abc1779d924235e6938a5c35e7428f5916eec38c64ea34ec18217f2 4605383 2017-04-25 23:09:17 HRYCxScEBr8R4eLRc9zwsmU8jX8gvcoM6a 2947478457.86640000 5.6.1.2. HTML5 9699446ff34e6224a177df2566c6503f791330256601c7126ad10ed225c61b3b 4604813 2017-04-25 16:16:14 HTENYcoKi3NYM13AhwrjzsEN9AGnVYYYui 2852036157.86640000 5.6.1.3. Total: 5799514615.73279954 HTML5 5.7. Activity and Identity of the Hacker.
Username yanmar E-mail [email protected] ::: LOGIN 2017-04-25 16:06:56.578353+00 ::: --- IP 146.185.31.214 ::: --- LAST ACTIVITY 2017-04-26 00:49:30.656994+00 ::: --- TIMEZONE -3 ::: --- BROWSER Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36 ::: --- LANGS en-US,en;q=0.8 ::: LOGIN 2017-04-25 12:14:44.607931+00 ::: --- IP 37.130.229.149 ::: --- LAST ACTIVITY 2017-04-25 15:40:26.436481+00 ::: --- TIMEZONE -3 ::: --- BROWSER Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36 ::: --- LANGS en-US,en;q=0.8
Withdraws to: HKW9SyBMMqmvqtFVt62M38p1DB3E7fPtN6 H8gG3N12VBxkTGXvVNnU8h14ZvivYDVSVs HMQ85E73ckbVX5km3531HfMk4Kn8egmmpV H9fcC7c4UpjABeAGKpaac1KFehjz6Ft5aX HJ6AeP636JQMt8HqtaDvUYggupZ7U3uh5t HUBWDWrMvxAwtAbKB48RAVrCZgwnqqbk51 HFncs5hxUFvxnieNqWC48xrVjYtTijb7Jj HQmwFURL5Rkb43gRNitKd5RfW4zZ2NNMcC
5.8. We understand that this is a challenge for both Bleutrade and HTMLCOIN Community. Because of this, we are here to cooperate with Bleutrade in resolving this enigma. We maintain open communication with Bleutrade.
  1. Summary of the meeting and Implications of our decision as a community. 6.1. Reversing the blockchain will do more harm than good. 6.2. Because we decided not to rollback the blockchain, all coins outside of Bleutrade, specifically in Yo Bit and Coin Gather, it will not turn to zero, they are legitimate. 6.3. We have instructed Yo Bit and Coin Gather to resume trading. 6.4. We are releasing an updated Windows Wallet, Mac Wallet, Blockchain File, and the HTMLCOIN account in GitHub. 6.5. We understand that the Attacker Deposited 5.7 Billion to Bleutrade. 6.6. That the attacker was denied by the network. 6.7. That the 2 deposits were deleted from the Blockchain. 6.8. That we need to understand more about the Bleutrades Insolvency Enigma and we are willing to cooperate in solving this issue. 6.9. The attack that happened in Bleutrade is not an isolated case to HTMLCOIN. Other cryptocurrencies in Bleutrade were also a victim of a similar attack, such as Virtacoin, Ambercoin, et cetera. 6.10. That we have the identity of the hacker. 6.11. We are maintaining open communication to Bleutrade to explore possible solutions. 6.12. Given with this experience, we are now implementing real-time checkpointing moving forward so that the will withstand possible attacks a feature that will make HTMLCOIN stronger in the future ahead.
SOURCE: https://docs.google.com/document/d/1JpkQpDVzDeU2C2tgwSh7I31VBEuy4eXiFY2kR36KFiM/edit?usp=sharing
submitted by htmlcoinbrasil to htmlcoin_community [link] [comments]

Looking For Someone To Help Build A Block Explorer

We are looking for someone to help us build a block explorer for our website. The open source explorer we are looking at is: https://github.com/bitcoin-abe/bitcoin-abe
If you are capable of guiding us through the install, please comment here or send me a PM.
Thank you.
submitted by YokoHamata to Bitcoin [link] [comments]

Bitcoin transaction history data sets

I'm working on a Machine Learning project of predicting Bitcoin Prices, taking inspiration from this MIT study: http://news.mit.edu/2014/mit-computer-scientists-can-predict-price-bitcoin.
I'm looking for publicly available data sets of transaction history in large quantity. The people in the above study "used data related to price and order book obtained from Okcoin.com. The order book data consists of 60 best prices at which one is willing to buy or sell at a given point of time. The data points were acquired at the interval of every two seconds for 6 months, for a total of 200 million data points".
I'm new to this area so on this site and others like blockchain.info, I've only been able to see the transactions, don't know how to download them. Something in .csv format would be ideal.
Any suggestions would be appreciated. Thank you!
P.S - I came across ABE (https://github.com/bitcoin-abe/bitcoin-abe) to parse the block files, but obviously need the block files (apparently in .dat format) first.
submitted by ShadyRedDevil to Bitcoin [link] [comments]

Blockchain analysis basics

There are a few useful tools if you have an interest in digging through Bitcoin's blockchain.
For casual digging, there's:
For more serious analysis, you'll need a copy on your local system and a good amount of memory.
If you run the main bitcoin client, it will download a local copy (all 18GB currently).
There are a couple of tools that will work with these files:
Alternatively, you can grab a copy of a database dump:
For other formats like SQLite and MySQL, you can run Abe but you'll need to have a copy of the blockchain already downloaded for it to process.
Since the quickest way to get going locally is probably the postgres route, here's what I recently did:
Once that's all done, load up psql:
psql -U postgres blockchain 
I suggest adding a few extra indexes. I started off looking for patterns in transfer amounts, so I added an index on value to the txout table.
create index txout_value_index on txout(value) 
Browsing the blockchain, I'd noticed a few transactions for 0.031337 BTC in the chain going from one of the Mt Gox addresses, so I wanted to know how often this value was used.
select * from txout where value = 3133700; 
One of the patterns identified on another reddit thread mentioned transactions involving 4000BTC preceeded by 0.001 BTC moving in and then back. Here's how to find that pattern:
COPY (select * from txout as txo join addr_txout on txo.id = addr_txout.txout_id join addr on addr.id = addr_txout.addr_id where value = 400000000000) to '/tmp/fourk' with csv header; COPY (select * from txout as txo join addr_txout on txo.id = addr_txout.txout_id join addr on addr.id = addr_txout.addr_id where value = 400000000000) to '/tmp/change' with csv header; => 309 rows cat /tmp/fourk | cut -f 10 -d',' | sort | uniq | xargs -J % -n 1 grep % /tmp/change > fourandchange 
submitted by polyclef to Bitcoin [link] [comments]

Setting up bitcoin-abe for defcoin

here's my notes on installing abe for blockchain explorer. YMMV ;)
14.04 ubuntu sudo apt-get install screen build-essential libssl-dev libboost1.55-all-dev libdb5.3-dev libdb5.3++-dev libminiupnpc-dev mysql-client mysql-server git clone https://github.com/tiabguls/defcoin.git cd defcoin/src make -f makefile.unix cp defcoind ~/ edit ~/.defcoin/defcoin.conf ==defcoin.conf== rpcuser=someuser rpcpassword=somepassword alertnotify=echo %s | mail -s "defcoin Alert" [email protected] txindex=1 ================ run screen start defcoind ~/defcoind -seednode=seed2.defcoin.org -reindex detach (ctrl-a-d) sudo apt-get install python2.7 python-crypto python-mysqldb git clone https://github.com/bitcoin-abe/bitcoin-abe.git (see https://github.com/bitcoin-abe/bitcoin-abe/blob/masteREADME-MYSQL.txt ) create mysql user & database cd bitcoin-abe find magic number https://bitcointalk.org/index.php?topic=131781.0 main.cpp of defcoin unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // defcoin: increase each by adding 2 to bitcoin's value. find address version https://github.com/bitcoin-abe/bitcoin-abe/blob/mastedoc/FAQ.html edit abe.conf ==abe.conf== default-loader = blkfile dbtype MySQLdb connect-args {"user":"abe","db":"abe","passwd":"somepassword"} port 2750 host 0.0.0.0 upgrade datadir += [{ "dirname": "/home/user1234/.defcoin", "code3": "DFC", "address_version": "\u001e", "magic": "xfbxc0xb6xdb", "chain": "Defcoin" }] =========== 
Load abe data
python -m Abe.abe --config=/path/to/abe.conf --commit-bytes 100000 --no-serve 
Rescan abe data (if needeD)
python -m Abe.abe --config=/path/to/abe.conf --rescan 
Run web server
python -m Abe.abe --config=/path/to/abe.conf 
should be up and listening on port 2750.
submitted by embalmed to defcoin [link] [comments]

Could someone help my get hold of an SQL dump of the blockchain?

I'm a programmer, and I want to do a bunch of analysis/visualisation on the evolution of the blockchain.
I've tried to get Abe and Blockparser compiled/installed/working, to no avail. I'm at a bit of a loss here, because all of these tools are outside my comfort zone (C#), so debugging is going to take ages.
Does anyone have the ability to share an up to date ish (ie this year) SQL dump of the blockchain with me? I run Bitcoin-Qt, so I have the 30GB blockchain knocking around on disk.
Thanks, and sorry if I'm posting in the wrong place.
submitted by BrassTeacup to Bitcoin [link] [comments]

[Hiring] Altcoin Developer

I need a developer to pull from github and develop a block-explorer website, bitcoind wallet, paper wallet generator and bitcoind android app.
Here are the github repos: https://github.com/bitcoin-abe/bitcoin-abe https://bitcoin.org/bin/0.8.6/bitcoin-0.8.6-linux.tar.gz https://github.com/cantonbeckebitcoinpaperwallet https://code.google.com/p/bitcoin-wallet/
Setup on Amazon EC2. Message me if you can do a part of it but not the other, we can work out rates for each part.
submitted by bittycoin to Jobs4Bitcoins [link] [comments]

[PYTHON] Adding a API call to ABE block browser

I need a somewhat experienced Python dev who adds the Blockchain.info-'Multi Address' API call (http://blockchain.info/multiaddr?active=$address|$address (Multiple addresses divided by |)) to the existing open source block explorer (https://github.com/bitcoin-abe/bitcoin-abe).
Write me a message with your contacts and a little bit more about yourself for more details. PGP encryption prefered.
You can earn some extra money if you help me with the server administration, i.e. managing different blockchains inside virtual machines on cloud servers.
submitted by Priming to Jobs4Bitcoins [link] [comments]

History of Bitcoin 2009-2018 (Git Visualization) Litecoin: Dead or Developed? GitHub Exposed! Can You Rely on GitHub Data?? Searching for Bitcoins in GitHub repositories with Google BigQuery Bitcoin GitHub and Charts - Good Morning Crypto - Programmer explains Why Build on Bitcoin Cash: A Bitcoin ABC Livestream - YouTube

Current Description . Abe (aka bitcoin-abe) through 0.7.2, and 0.8pre, allows XSS in __call__ in abe.py because the PATH_INFO environment variable is mishandled during a PageNotFound exception. Bitcoin-Abe has 2 repositories available. Follow their code on GitHub. For usage, run "python -m Abe.abe --help" and see the comments in abe.conf. You will have to specify a database driver and connection arguments (dbtype and connect-args in abe.conf). The dbtype is the name of a Python module that supports your database. Trade Bitcoin's over my old hacked wallet!!!! Nov 13, 2019 : blackmail scam : Chen : He scammed me to send him all my bitcoins : Nov 13, 2019 : blackmail scam : Celeste shuette : He's a scammer , stole someone else's money and put it in my bank to buy bitcoin as part of his scheme , hiring me as an assistant to transfer money to bitcoin : Nov Date Abuse Type Abuser Description; Jun 21, 2020 : ransomware : Xenia Freimont; [email protected] Had an old password of mine and said malware was used to record me looking at porn sites.

[index] [24991] [1880] [30944] [27316] [10156] [6655] [14679] [10627] [19244] [21899]

History of Bitcoin 2009-2018 (Git Visualization)

#bitcoin #crypto #btc #github #ethereum #eth #cryptocurrency #blockchain #wealth #rich #money #invest #hodl #altcoin #forex **Disclaimer** The information contained herein is for informational ... Bitcoin GitHub and Charts - Good Morning Crypto - Programmer explains - Duration: 19:27. Ivan on Tech 11,389 views. 19:27. Best Binary Options Strategy 2020 - 2 Minute Strategy LIVE TRAINING ... ----- Bitcoin Source Codes ----- The bitcoin Github release page - versions 0.1.5 to 0.15: https://github.com/bitcoin/bitcoin/releases A copy of the first or... #litecoin #bitcoin #crypto #btc #ltc #cryptocurrency #altcoin #altcoins #ethereum #eth #blockchain #github #wealth #money #rich The information contained herein is for informational purposes only. How To Use A Bitcoin Hardware Wallet: Ledger Nano X - Duration: 39:02. BTC Sessions 40,390 views. 39:02. How To Use NikeShoeBot "NSB" - Full Bot Tutorial Explained 2020 Edition - Duration: 27:07.

Flag Counter