Search content
Sort by
Showing 20 of 33 results by naufragus
a function to validate Testnet WIF ,
This is not how you should "validate" a WIF though. The string length and starting character are not important to the code (only for readability).What you should do is [...]
Thanks, pooya87! I now understand the correct validation method of Private Addresses. That info is really useful but also made me aware I really only need a pattern check, as kano explained.
NotATether was nice, too. I never found that regex in Binance API docs but I did not read those docs thoroughly when I was messing with them. All the discussion about the pattern regex was interesting (I know you guys are making history here) and I was able to add the mainnet uppercase BC1 regex to my collection as that case was not covered yet. Cheers!
OK, I reckon that regex is working when adding the right prefixes in the character list.
Sorry guys. I cannot remove this thread from this board, which I thought was the right one for the question.
But I suggest the moderator to remove it.
Sorry guys. I cannot remove this thread from this board, which I thought was the right one for the question.
But I suggest the moderator to remove it.
I am writing a script for dealing with bitcoin hashing and it would be useful to have a function to validate Testnet WIF pubkeys, both uncompressed (starting with 9) and compressed (starting with c), such as:
92Pg46rUhgTT7romnV7iGW6W1gbGdeezqdbJCzShkCsYNzyyNcc
cNJFgo1driFnPcBdBX8BrJrpxchBWXwXCvNH5SoSkdcF6JXXwHMm
https://en.bitcoin.it/wiki/List_of_address_prefixes
I have got regexes for most of other types of addresses, including regexes for mainet WIF types but they don't seem to match if I merely add [9c] to the prefix list.. I read somewhere that prefix and ending of testnet WIFs are different from those of mainet. Below is the regex for mainet WIFs I ahve got and which does not work.
If you guys know a regex that could work with testnet WIFs, please let me know. Or point to a page of testnet WIFs I can check and try something myself (could not find on Google anything that helped me yet)..
Cheers
92Pg46rUhgTT7romnV7iGW6W1gbGdeezqdbJCzShkCsYNzyyNcc
cNJFgo1driFnPcBdBX8BrJrpxchBWXwXCvNH5SoSkdcF6JXXwHMm
https://en.bitcoin.it/wiki/List_of_address_prefixes
I have got regexes for most of other types of addresses, including regexes for mainet WIF types but they don't seem to match if I merely add [9c] to the prefix list.. I read somewhere that prefix and ending of testnet WIFs are different from those of mainet. Below is the regex for mainet WIFs I ahve got and which does not work.
Code:
[5KL][1-9A-HJ-NP-Za-km-z]{50,51}
If you guys know a regex that could work with testnet WIFs, please let me know. Or point to a page of testnet WIFs I can check and try something myself (could not find on Google anything that helped me yet)..
Cheers
Checking the License is important.
All lawyers can dig that..
It is fearful misunderstanding what `open source' means.
If you think `open source' means that you can check the source code,
there is a long way ahead..
All lawyers can dig that..
It is fearful misunderstanding what `open source' means.
If you think `open source' means that you can check the source code,
there is a long way ahead..
You can try blockchain.com:
I have got a shell script called binfo.sh[/t]] which does some API calls and format the data.
https://github.com/mountaineerbr/markets/blob/master/binfo.sh
Code:
% curl -L --compressed "https://blockchain.info/rawaddr/[ADDR_HERE]" | jq
I have got a shell script called binfo.sh[/t]] which does some API calls and format the data.
https://github.com/mountaineerbr/markets/blob/master/binfo.sh
The most generic and correct term is `Free Software'. Bitcoin is free software, not open source.
Open source software has got no philosophy involved and pointing users to it
is a big problem because they will only get a fraction of what the
Free Software Movement is all about..
Open source software has got no philosophy involved and pointing users to it
is a big problem because they will only get a fraction of what the
Free Software Movement is all about..
There's a documentary ...
Thanks for that link reference! That is really good.
I did restart the node after changing configs.
Will reboot the server and start ONLY bitcoind to be sure that no other service is interfering with its RAM usage, just to be sure..
That is a Manjaro system updated in the beginning of the month with latest version.
The config file is located in a usd hd together with blockchain data.
The command I use to start the daemon as a normal user is:
Now that I know that is not the expected RAM usage, I will try to investigate it in the following days.
Thanks for the answers. In the meantime, I will be checking this thread and will report later.
Thanks guys!
No, it's not normal behavior. Can you share command you use to run bitcoind?
Have you restarted the node after adding the configurations? Because you have to.
Have you restarted the node after adding the configurations? Because you have to.
Thanks for that link reference! That is really good.
I did restart the node after changing configs.
Will reboot the server and start ONLY bitcoind to be sure that no other service is interfering with its RAM usage, just to be sure..
No, it's not normal behavior. Can you share command you use to run bitcoind?
That is a Manjaro system updated in the beginning of the month with latest version.
The config file is located in a usd hd together with blockchain data.
The command I use to start the daemon as a normal user is:
Code:
% bitcoind -conf=/media/usdhd/blockchain/bitcoin.conf
Now that I know that is not the expected RAM usage, I will try to investigate it in the following days.
Thanks for the answers. In the meantime, I will be checking this thread and will report later.
Thanks guys!
⭐ Merited by DdmrDdmr (1)
I am setting a home server for multiple purposes.
However, bitcoind using using a lot of RAM.
I wish to limit resource usage as I would prefer more RAM
was available for other tasks as well..
I tried setting some configs as per the following post:
https://bitcoin.stackexchange.com/questions/50580/how-to-run-bitcoind-in-a-low-memory-environment
Is there anything else I can do or is that just bitcoind normal behaviour to consume as much RAM as the kernel will let it have?
Here are my configs:
And here is htop output:
https://imgur.com/a/wXjtqPL
However, bitcoind using using a lot of RAM.
I wish to limit resource usage as I would prefer more RAM
was available for other tasks as well..
I tried setting some configs as per the following post:
https://bitcoin.stackexchange.com/questions/50580/how-to-run-bitcoind-in-a-low-memory-environment
Is there anything else I can do or is that just bitcoind normal behaviour to consume as much RAM as the kernel will let it have?
Here are my configs:
Code:
datadir=/media/usbhd/blockchain
txindex=1
rpcuser=XXX
rpcpassword=YYY
dbcache=300
onlynet=onion
listen=0
listenonion=0
maxconnections=8
proxy=127.0.0.1:9050
discover=0
txindex=1
rpcuser=XXX
rpcpassword=YYY
dbcache=300
onlynet=onion
listen=0
listenonion=0
maxconnections=8
proxy=127.0.0.1:9050
discover=0
Code:
% free -h
total used free shared buff/cache available
Mem: 5,7Gi 4,1Gi 1,1Gi 6,0Mi 419Mi 1,3Gi
Swap: 3,9Gi 660Mi 3,3Gi
total used free shared buff/cache available
Mem: 5,7Gi 4,1Gi 1,1Gi 6,0Mi 419Mi 1,3Gi
Swap: 3,9Gi 660Mi 3,3Gi
And here is htop output:
https://imgur.com/a/wXjtqPL
Re: List of all Bitcoin addresses ever used - currently available on temp location
⭐ Merited by adaseb (1)
Just to let you guys know i updated my bitcoin-all-addresses list.
That is available in my github repo https://github.com/mountaineerbr/bitcoin-all-addresses
All addresses are uniquely printed in the order they first appeared in Blockchair output dumps.
I was able to reproduce my methodology after 6 moths from the first lists.
The methodology is described in the read me of the git repo
and some code i used here: https://github.com/mountaineerbr/bitcoin-all-addresses/blob/master/blockchair.btcoutputs.process.sh
If you export LANG=C and LC_ALL=C, that will speed up sorting and as we are dealing
with base58 and segwit base addresses, that should be OK.
That is available in my github repo https://github.com/mountaineerbr/bitcoin-all-addresses
All addresses are uniquely printed in the order they first appeared in Blockchair output dumps.
I was able to reproduce my methodology after 6 moths from the first lists.
The methodology is described in the read me of the git repo
and some code i used here: https://github.com/mountaineerbr/bitcoin-all-addresses/blob/master/blockchair.btcoutputs.process.sh
If you export LANG=C and LC_ALL=C, that will speed up sorting and as we are dealing
with base58 and segwit base addresses, that should be OK.
If you are using Linux shell and run my script (bitcoin.tx.sh):
The script uses grondilu's bitcoin-bash-tools to make the address from the pub key..
Script from my githubh repo: https://github.com/mountaineerbr/scripts/blob/master/bitcoin.tx.sh
Code:
user@archhost ~ % bitcoin.tx.sh a64be218809b61ac67ddc7f6c7f9fbebfe420cf75fe0318ebc727f060df48b37
txs: 1/1
backing up existing result file..
renamed '/home/user/00.transactions.parsed.txt' -> '/home/user/00.transactions.parsed.txt.1605976409.bak'
--------
Transaction information
TxId____: a64be218809b61ac67ddc7f6c7f9fbebfe420cf75fe0318ebc727f060df48b37
Hash____: a64be218809b61ac67ddc7f6c7f9fbebfe420cf75fe0318ebc727f060df48b37
BlkHash_: 0000000049a63b4dda3a43450c19d085d6c28bfb4cbb2e0576815d7f31919c5d
Time____: 1233636459 2009-02-03T04:47:39Z
BlkTime_: 1233636459 2009-02-03T04:47:39Z
LockTime: 0
Version_: 1
Vsize___: 276
Size____: 276
Weight__: 1104
Confirma: 650779
Vins
TxIndex: 131f68261e28a80c3300b048c4c51f3ca4745653ba7ad6b20cc9188322818f25
Sequenc: 4294967295
VoutNum: 1
Addresses
Number_: 1 Value__: 49.99
type: pubkey
1AbHNFdKJeVL8FRZyRZoiTzG9VCmzLrtvm
Vouts
Number_: 0 Value__: 0.01
Addresses
type: pubkey
1CbAopr7sNMKjsJa8dAS6P5sM788kmMooo
Number_: 1 Value__: 49.98
Addresses
type: pubkey
1AbHNFdKJeVL8FRZyRZoiTzG9VCmzLrtvm
VinSum__: 49.99000000
VoutSum_: 49.99000000
TxFee___: 0
>>>final transaction parsing at: /home/user/00.transactions.parsed.txt
>>>temporary directory removed -- /dev/shm/bitcoin.tx.sh.116526.5TZ3VjAk
>>>took 1 seconds (0 minutes)
txs: 1/1
backing up existing result file..
renamed '/home/user/00.transactions.parsed.txt' -> '/home/user/00.transactions.parsed.txt.1605976409.bak'
--------
Transaction information
TxId____: a64be218809b61ac67ddc7f6c7f9fbebfe420cf75fe0318ebc727f060df48b37
Hash____: a64be218809b61ac67ddc7f6c7f9fbebfe420cf75fe0318ebc727f060df48b37
BlkHash_: 0000000049a63b4dda3a43450c19d085d6c28bfb4cbb2e0576815d7f31919c5d
Time____: 1233636459 2009-02-03T04:47:39Z
BlkTime_: 1233636459 2009-02-03T04:47:39Z
LockTime: 0
Version_: 1
Vsize___: 276
Size____: 276
Weight__: 1104
Confirma: 650779
Vins
TxIndex: 131f68261e28a80c3300b048c4c51f3ca4745653ba7ad6b20cc9188322818f25
Sequenc: 4294967295
VoutNum: 1
Addresses
Number_: 1 Value__: 49.99
type: pubkey
1AbHNFdKJeVL8FRZyRZoiTzG9VCmzLrtvm
Vouts
Number_: 0 Value__: 0.01
Addresses
type: pubkey
1CbAopr7sNMKjsJa8dAS6P5sM788kmMooo
Number_: 1 Value__: 49.98
Addresses
type: pubkey
1AbHNFdKJeVL8FRZyRZoiTzG9VCmzLrtvm
VinSum__: 49.99000000
VoutSum_: 49.99000000
TxFee___: 0
>>>final transaction parsing at: /home/user/00.transactions.parsed.txt
>>>temporary directory removed -- /dev/shm/bitcoin.tx.sh.116526.5TZ3VjAk
>>>took 1 seconds (0 minutes)
The script uses grondilu's bitcoin-bash-tools to make the address from the pub key..
Script from my githubh repo: https://github.com/mountaineerbr/scripts/blob/master/bitcoin.tx.sh
⭐ Merited by NotATether (2)
Hello guys!
It has been some months my working on some bash scripts
to get information of a transaction by its hash through bitcoin-cli
and parse the json data for that transaction in a more readable way.
(And also to learn some about bitcoin hashing).
As i wrote some wrappers for blockchain.com APIs, I wanted to get
more or less the same information for when quering for a transaction
or a block's worth of transaction.. I used functions from grondilu's
bitcoin-bash-tools..
Before trying the scripts, one needs have bitcoin-cli, openssl and jq
packages installed. Also, that is a very good idea to have bitcoin-cli
set with txindex=1 (otherwise you would need supply the block hash
for the transactions).
The scripts are at https://github.com/mountaineerbr/scripts/graphs/traffic
There are two scripts, one for getting block information and transaction
hashes in that block, and another to get transaction information by
transaction hash. For example:
Get info of a transaction by its hash id:
The output:
One can parse all transactions from a block using my two scripts, such as:
The problem is this script is slow to parse all transactions from a block, such
as in the previous example, because each transaction may require more
than a single RPC call to get extra information from previous UTXOs..
It took about 10 minutes to completely parsing all 1660 transactions from
block 400000 with my i7 (blockchain data is in an external USD HDD)..
However, for few dozen transactions I reckon using that is quite feasible,
or maybe I just think that is an interesting script..
The scripts and more examples are at https://github.com/mountaineerbr/scripts/graphs/traffic
Cheers,The scripts are at https://github.com/mountaineerbr/scripts/graphs/traffic
It has been some months my working on some bash scripts
to get information of a transaction by its hash through bitcoin-cli
and parse the json data for that transaction in a more readable way.
(And also to learn some about bitcoin hashing).
As i wrote some wrappers for blockchain.com APIs, I wanted to get
more or less the same information for when quering for a transaction
or a block's worth of transaction.. I used functions from grondilu's
bitcoin-bash-tools..
Before trying the scripts, one needs have bitcoin-cli, openssl and jq
packages installed. Also, that is a very good idea to have bitcoin-cli
set with txindex=1 (otherwise you would need supply the block hash
for the transactions).
The scripts are at https://github.com/mountaineerbr/scripts/graphs/traffic
There are two scripts, one for getting block information and transaction
hashes in that block, and another to get transaction information by
transaction hash. For example:
Get info of a transaction by its hash id:
Code:
$ bitcoin.tx.sh a8bb9571a0667d63eaaaa36f9de87675f0d430e13c916248ded1d13093a77561
The output:
Code:
--------
Transaction information
TxId____: a8bb9571a0667d63eaaaa36f9de87675f0d430e13c916248ded1d13093a77561
Hash____: eac5391d9f7b411c7d6cbadb59a38bfa13399c3ecb440573f5f52b8a34001be1
BlkHash_: 0000000000000000000fb6a4d6f5dc7438f91a1bc3988c4f32b4bb8284eed0ec
Time____: 1594156611 2020-07-07T21:16:51Z
BlkTime_: 1594156611 2020-07-07T21:16:51Z
LockTime: 0
Version_: 1
Vsize___: 224
Size____: 414
Weight__: 894
Confirma: 12546
Vins
TxIndex: 44f672f301772cf3e3fc15d424818aae8ed43468deb0cc56550dd9374578b816
Sequenc: 4294967295
VoutNum: 1
Addresses
Number_: 1 Value__: 4.68295
type: witness_v0_scripthash
bc1qwqdg6squsna38e46795at95yu9atm8azzmyvckulcc7kytlcckxswvvzej
Vouts
Number_: 0 Value__: 0.26139693
Addresses
type: scripthash
3KLwdgGf5QLHEW8qjxyv7wFpPMdVCDqu55
Number_: 1 Value__: 0.19883951
Addresses
type: pubkeyhash
1Lv9hU7h86REpDakYy9kpeTfT929b9twM5
Number_: 2 Value__: 4.22231356
Addresses
type: witness_v0_scripthash
bc1qwqdg6squsna38e46795at95yu9atm8azzmyvckulcc7kytlcckxswvvzej
Transaction information
TxId____: a8bb9571a0667d63eaaaa36f9de87675f0d430e13c916248ded1d13093a77561
Hash____: eac5391d9f7b411c7d6cbadb59a38bfa13399c3ecb440573f5f52b8a34001be1
BlkHash_: 0000000000000000000fb6a4d6f5dc7438f91a1bc3988c4f32b4bb8284eed0ec
Time____: 1594156611 2020-07-07T21:16:51Z
BlkTime_: 1594156611 2020-07-07T21:16:51Z
LockTime: 0
Version_: 1
Vsize___: 224
Size____: 414
Weight__: 894
Confirma: 12546
Vins
TxIndex: 44f672f301772cf3e3fc15d424818aae8ed43468deb0cc56550dd9374578b816
Sequenc: 4294967295
VoutNum: 1
Addresses
Number_: 1 Value__: 4.68295
type: witness_v0_scripthash
bc1qwqdg6squsna38e46795at95yu9atm8azzmyvckulcc7kytlcckxswvvzej
Vouts
Number_: 0 Value__: 0.26139693
Addresses
type: scripthash
3KLwdgGf5QLHEW8qjxyv7wFpPMdVCDqu55
Number_: 1 Value__: 0.19883951
Addresses
type: pubkeyhash
1Lv9hU7h86REpDakYy9kpeTfT929b9twM5
Number_: 2 Value__: 4.22231356
Addresses
type: witness_v0_scripthash
bc1qwqdg6squsna38e46795at95yu9atm8azzmyvckulcc7kytlcckxswvvzej
One can parse all transactions from a block using my two scripts, such as:
Code:
$ bitcoin.blk.sh -ii 400000 | bitcoin.tx.sh
The problem is this script is slow to parse all transactions from a block, such
as in the previous example, because each transaction may require more
than a single RPC call to get extra information from previous UTXOs..
It took about 10 minutes to completely parsing all 1660 transactions from
block 400000 with my i7 (blockchain data is in an external USD HDD)..
However, for few dozen transactions I reckon using that is quite feasible,
or maybe I just think that is an interesting script..
The scripts and more examples are at https://github.com/mountaineerbr/scripts/graphs/traffic
Cheers,The scripts are at https://github.com/mountaineerbr/scripts/graphs/traffic
Seems that api is stuck for now..
You cna try this but does not go as far back (until 2013-04-28)
and will stop working at any time:
You cna try this but does not go as far back (until 2013-04-28)
and will stop working at any time:
Code:
$ curl https://www.coingecko.com/price_charts/export/bitcoin/usd.csv
Hey, i wrote my methodology in my github repo for my addresses list..
Anyways, here is what i did..
Note that using LC_ALL=C will greatly speed up sorting!
Anyways, here is what i did..
Code:
$ nl concat.txt | TMPDIR='/large/tmp/dir' LC_ALL=C sort -k2 -u | sort -n | cut -f2 > final.txt
Note that using LC_ALL=C will greatly speed up sorting!
NastyFans gathers a daily exchange rate from multiple sources to use for statistical conversion data on charts. This information is posted publicly so that anyone may utilize it and dates all the way back to July of 2010! Enjoy!
https://nastyfans.org/exchangerate.csv
https://nastyfans.org/exchangerate.csv
That is a very nice API..
Nastyfans.org is a pool? Hope they live long and keep this api up..
I love to check a snapshot-price from the terminal, coin market cap
and coingecko apis i use only go back to ~2014 max..
Thanks!
Re: Linux command line tool for Bitcoin / crypto quotes (bash)
Hi all,
I wrote a small linux command line tool as a bash scripting learning project; it uses the CoinGecko-API and is capable of displaying all their supported crypto-currencies, as well as cross-currencies (>50 at the moment, including some cryptos and commodities gold and silver).
Enjoy!
I wrote a small linux command line tool as a bash scripting learning project; it uses the CoinGecko-API and is capable of displaying all their supported crypto-currencies, as well as cross-currencies (>50 at the moment, including some cryptos and commodities gold and silver).
Enjoy!
Hey mate, nice script! I was very interested when i saw the topic here..
I wrote some scripts for similar purposes and you may be interested.
https://github.com/mountaineerbr/markets
Specially, i wrote the cgk.sh which uses CoinGecko API, too.
Syntax is something like:
Code:
$ cgk.sh 5+5 BTC CNY
804340.0000000000000000
804340.0000000000000000
It has many options and i hope it is robust, however if the user is not
connected to the internet or the error is from CoinGecko side, i dont care
to troubleshoot for the user too much..
I actually can 
I found this regexp on Stackoverflow:
I found this regexp on Stackoverflow:Code:
egrep --regexp="^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$" filename
With some slight changes it stops matching parts of Eth-addresses:Code:
egrep -w --regexp="[13][a-km-zA-HJ-NP-Z1-9]{25,34}" *
I have compiled these from various sources:
#cryptocurrency greps
Code:
#btc1 and btc2 combined
alias btcgrep="grep -Ee '\b[13][a-km-zA-HJ-NP-Z1-9]{25,34}\b' -e '\bbc(0([ac-hj-np-z02-9]{39}|[ac-hj-np-z02-9]{59})|1[ac-hj-np-z02-9]{8,87})\b'"
#legacy addresses only
alias btcgrep1="grep -E '\b[13][a-km-zA-HJ-NP-Z1-9]{25,34}\b'"
#http://mokagio.github.io/tech-journal/2014/11/21/regex-bitcoin.html
#bech32 v1 and v0 addresses
alias btcgrep2="grep -E '\bbc(0([ac-hj-np-z02-9]{39}|[ac-hj-np-z02-9]{59})|1[ac-hj-np-z02-9]{8,87})\b'"
#https://stackoverflow.com/questions/21683680/regex-to-match-bitcoin-addresses
#bech32 addresses only
alias btcgrep3="grep -E '\bbc1[ac-hj-np-zAC-HJ-NP-Z02-9]{11,71}\b'"
#both legacy and bech32
alias btcgrep4="grep -E '\b([13][a-km-zA-HJ-NP-Z1-9]{25,34}|bc1[ac-hj-np-zAC-HJ-NP-Z02-9]{11,71})\b'"
#http://mokagio.github.io/tech-journal/2014/11/21/regex-bitcoin.html
#private keys
alias btcgrep5="grep -E '\b[5KL][1-9A-HJ-NP-Za-km-z]{50,51}\b'"
#word boundary: '\b'
#https://bitcoin.stackexchange.com/questions/56737/how-can-i-find-a-bitcoin-private-key-that-i-saved-in-a-text-file
#transaction hashes
alias btcgrep6="grep -E '\b[a-fA-F0-9]{64}\b'"
#https://stackoverflow.com/questions/46255833/bitcoin-block-and-transaction-regex
#https://bitcoin.stackexchange.com/questions/70261/recognize-bitcoin-address-from-block-hash-and-transaction-hash
#block hashes
alias btcgrep7="grep -E '\b[0]{8}[a-fA-F0-9]{56}\b'"
#https://stackoverflow.com/questions/46255833/bitcoin-block-and-transaction-regex
#ethereum address hash
#test for 'plausibility'
alias ethgrep="grep -E '\b(0x)?[0-9a-fA-F]{40}\b'"
#https://ethereum.stackexchange.com/questions/1374/how-can-i-check-if-an-ethereum-address-is-valid
#ethereum transaction hash
alias ethgrep2="grep -E '\b(0x)?([A-Fa-f0-9]{64})\b'" #parentheses are not necessary
#https://ethereum.stackexchange.com/questions/34285/what-is-the-regex-to-validate-an-ethereum-transaction-hash/34286
alias btcgrep="grep -Ee '\b[13][a-km-zA-HJ-NP-Z1-9]{25,34}\b' -e '\bbc(0([ac-hj-np-z02-9]{39}|[ac-hj-np-z02-9]{59})|1[ac-hj-np-z02-9]{8,87})\b'"
#legacy addresses only
alias btcgrep1="grep -E '\b[13][a-km-zA-HJ-NP-Z1-9]{25,34}\b'"
#http://mokagio.github.io/tech-journal/2014/11/21/regex-bitcoin.html
#bech32 v1 and v0 addresses
alias btcgrep2="grep -E '\bbc(0([ac-hj-np-z02-9]{39}|[ac-hj-np-z02-9]{59})|1[ac-hj-np-z02-9]{8,87})\b'"
#https://stackoverflow.com/questions/21683680/regex-to-match-bitcoin-addresses
#bech32 addresses only
alias btcgrep3="grep -E '\bbc1[ac-hj-np-zAC-HJ-NP-Z02-9]{11,71}\b'"
#both legacy and bech32
alias btcgrep4="grep -E '\b([13][a-km-zA-HJ-NP-Z1-9]{25,34}|bc1[ac-hj-np-zAC-HJ-NP-Z02-9]{11,71})\b'"
#http://mokagio.github.io/tech-journal/2014/11/21/regex-bitcoin.html
#private keys
alias btcgrep5="grep -E '\b[5KL][1-9A-HJ-NP-Za-km-z]{50,51}\b'"
#word boundary: '\b'
#https://bitcoin.stackexchange.com/questions/56737/how-can-i-find-a-bitcoin-private-key-that-i-saved-in-a-text-file
#transaction hashes
alias btcgrep6="grep -E '\b[a-fA-F0-9]{64}\b'"
#https://stackoverflow.com/questions/46255833/bitcoin-block-and-transaction-regex
#https://bitcoin.stackexchange.com/questions/70261/recognize-bitcoin-address-from-block-hash-and-transaction-hash
#block hashes
alias btcgrep7="grep -E '\b[0]{8}[a-fA-F0-9]{56}\b'"
#https://stackoverflow.com/questions/46255833/bitcoin-block-and-transaction-regex
#ethereum address hash
#test for 'plausibility'
alias ethgrep="grep -E '\b(0x)?[0-9a-fA-F]{40}\b'"
#https://ethereum.stackexchange.com/questions/1374/how-can-i-check-if-an-ethereum-address-is-valid
#ethereum transaction hash
alias ethgrep2="grep -E '\b(0x)?([A-Fa-f0-9]{64})\b'" #parentheses are not necessary
#https://ethereum.stackexchange.com/questions/34285/what-is-the-regex-to-validate-an-ethereum-transaction-hash/34286
Flag -w is 'word bondary' and can also be set within the regex with '\b' at the ends.
Very good work on compiling those addresses, mate!
I made List of all Bitcoin addresses ever used.
So for now, I gave up trying to keep addresses in chronological order. I'll keep the original data in case I find a different solution (or enough RAM) later.
one feature of my lists is i tried to keep the original order in which addresses first appeared in the blockchair dumps..
It works with awk:Code:
awk '!a[$0]++'
But this requires far too much memory. I can use this on data per day, but not on all data.So for now, I gave up trying to keep addresses in chronological order. I'll keep the original data in case I find a different solution (or enough RAM) later.
Hey that is very nice , bro.
You have got the means, work hard and is very good at it.
I knew that awk one-liner you wrote, tho i tried using perl because thought that might need less ram..
The sort command can keep chronological order without using ram but it needs a large temp directory (/tmp will not work as it is limited by the system ram value).
ok, cheers!