I noticed sentence "Powered by mempool.space and Coindesk." on your website. Have you checked whether those free API actually let user check thousand address within short time? All depends on how it is going to be used. If you want to test a bulk of addresses from time to time - then yes, maybe.
If you want to test 1 address every few (mili)seconds, it will be too slow, dedicated (and properly indexed) database will be better.
If OP goes on this route, he could load up the file into an optimized structure in memory (maybe b-tree?) at the start of the day and then just query his own structure every time. This should be quicker than using an actual database. Actual database also use optimized data structure (such as btree or trie), although it comes down to whether you can utilize it properly or not. |
|
|
|
When we change our BTC into another crypto and after change them back into BTC, I guess in this case it would no more be possible to trace back the origin of the origin BTC.
Am I right? Or do I miss anything?
Of course if we make the change on a CEX, it would be possible to trace back the origin, because the CEX will have a history-protocol. But I guess not, when we make this via DEX.
Aside from the fact some DEX is centralized, privacy/anonymity when using DEX also depends on how you use it. For example, interacting with DEX smart contract on ETH with lightweight wallet (such as Metamask) letting ETH node operator what you're doing. If I am right: Why do people use BTC mixer? Isn't changing BTC into another crypto and change them back, not the much better solution to cut off the trace?
If the process use DEX, there are several limitation such as small trading volume, waiting other participant to initiate the trade or bad exchange rate. |
|
|
|
IntroContinuing previous thread "Exploring alternative full node implementations - Gocoin"[1], this time i decide to try Bcoin[2]. I choose Bcoin since it's 4th fastest node implementation according to Jameson Lopp benchmark[3] and it has been around for some time. Basic information- Bcoin is written in JavaScript language.
- Bcoin is developed since 2014[4].
- Bcoin is built for businesses, miners, wallets, and hobbyists.
- Bcoin already used on business/production environment, including purse.io[5].
- Bcoin can be used either as full node, wallet (with some accounting feature), data API (through JSON-RPC) or JavaScript library.
My system- Debian-based OS
- Old 6 core CPU
- 32GB RAM
- 3.5" HDD (Both Bitcoin Core and Bcoin data stored here)
- Node.js v16.17.1
- Bitcoin Core 23.0
- Gocoin 2.2.0
Compile and installationThe documentation mention several requirement[6], but i already have all of them installed in my system. Although it surprise me Bcoin still support Node.js v10.0.0 which already reach end of life. The compile/installation process is very simple and i didn't experience any problem. git clone --depth=1 --branch=v2.2.0 https://github.com/bcoin-org/bcoin
cd bcoin/
npm rebuild
npm install
You can install Bcoin locally or globally. I decide to install it locally since i'd rather not mess with my system. But take note if you install it locally, bcoin binary is located inside directory bin where you ran npm install and bcoin binary is't available on $PATH[7]. Bcoin configurationTo configure Bcoin, there are 4 available options[8]. Those options are config file, CLI parameter, environment variable & JS object constructor. You also can combine them, but you'll have to pay attention to how Bcoin prioritize the configuration options. Bcoin have both node and wallet functionality, so you'll need to make 2 config file. If you check list of available configuration, you'll find out Bcoin have feature to index transaction and address. But since it could make initial sync/IBD longer, i decide not to enable those features. I decide to use config file, which is more convenient than typing long CLI parameter or messing with environment variable. If you use non-default directory path, you'll need to explicitly mention on wallet config file[9]. Aside from configuring Bcoin to only connect to my Bitcoin Core node, i try to make configuration which utilize 100% of my system. But there's no guarantee this is most optimal configuration. # bcoin.conf
workers: true
workers-size: 6
sigcache-size: 4000000
prefix: /path/to/bcoin/directory
max-files: 7000
cache-size: 16384
log-level: info
mempool-size: 300
replace-by-fee: true
persistent-mempool: true
port: 48333
only: 127.0.0.1:8333
http-port: 48332
api-key: test_bcoin
# wallet.conf
prefix: /path/to/bcoin/directory
http-port: 48334
I store both config file on directory which used to store blockchain and other files created by bcoin. In addition, i run bcoin on terminal by specifying directory path so bcoin locate config file automatically. ./bin/bcoin --prefix=/path/to/bcoin/directory
It took 9 days to complete initial sync/IBD until block 758232. But since i do not turn on my computer 24/7, actually it took about 90 hours 31 minutes (based on Bcoin log files). During sync i notice Bcoin ask for more block/data after few hours. So it's likely bcoin could sync faster if i turn on my computer 24/7.  Despite configuring bcoin to use all CPU and lots of RAM, bcoin doesn't use much of my system. I did not perform detailed logging, but i never see bcoin use more than 3.1GB of RAM and 300% CPU (according to htop). When i use iotop, i found out bcoin perform lots of disk read/write. After short monitoring with iotop -a, Bcoin perform 4.1GB read and 56.9GB write. This is clearly the reason Bcoin is far slower than gocoin during sync (6.8h[10] vs 90h31m). And talking about disk read/write, size of block/UTXO on Bcoin is only slightly bigger than Bitcoin Core. # Bitcoin Core
$ du -sh *
...
459G blocks
4.8G chainstate
...
# Bcoin
$ du -sh *
...
461G blocks
6.2G chain
...
After Bcoin finished initial sync/IBD, Bcoin begin to fill the mempool with unconfirmed transaction. What surprise me Bcoin print lots of error message with code "nonstandard" or "duplicate". After quick search, i found it might happen due to limited Taproot support[11], where only Bech32m address format is supported[12]. I also found out Bcoin isn't actively developed[13], which bring concern about future of Bcoin. (net) Error: Verification failure: bad-txns-inputs-spent (code=duplicate score=0 hash=de81bda3cd4a2d10efbe2133a9caa3cf7e36c71c1ba014dafbc2c80ccfdd1a01)
(net) Error: Verification failure: scriptpubkey (code=nonstandard score=0 hash=38911ac69ebdc26d6480115f1745d9800f4505cbf3cd17572003097f0f896ac6)
[1] https://bitcointalk.org/index.php?topic=5407675.0[2] https://bcoin.io/[3] https://blog.lopp.net/2021-bitcoin-node-performance-tests-2/[4] https://github.com/bcoin-org/bcoin#license[5] https://purse.io/shop, scroll down to bottom page to see text "Powered by bcoin" [6] https://github.com/bcoin-org/bcoin/blob/v2.2.0/docs/getting-started.md#requirements[7] https://github.com/bcoin-org/bcoin/blob/v2.2.0/docs/getting-started.md#starting-up-your-first-bcoin-node[8] https://github.com/bcoin-org/bcoin/blob/v2.2.0/docs/configuration.md[9] https://github.com/bcoin-org/bcoin/issues/645[10] https://bitcointalk.org/index.php?topic=5407675.0[11] https://github.com/bcoin-org/bcoin/issues/1032[12] https://github.com/bcoin-org/bcoin/pull/1038[13] https://github.com/bcoin-org/bcoin/issues/1044
|
|
|
|
I tried opening the website and got this error message "Gateway time-out Error code 504" by CloudFlare.
For me it worked (both clear net and tor link worked). I tried again and it worked this time. - We don't keeps logs.
Well, maybe you don't, but CloudFlare may do. Consider doing something about that. --snip-- I was going to say that earlier, but not 100% sure since the website use "Let's Encrypt" certificate. Anyway, i would recommend OP and everyone who visit this thread to read these discussion, Does CloudFlare proxy servers decrypt my data?Mixers using cloudflare's SSL certificates |
|
|
|
I tried opening the website and got this error message "Gateway time-out Error code 504" by CloudFlare. |
|
|
|
Is there a way (API?) to quickly check balance for thousands of public addresses?
Locally (Bitcoin Core) or via any market API?
FYI, Bitcoin Core isn't suitable for your needs. It lacks address index, so you'll need to use scantxoutset or import the address on wallet then rescan whole blockchain which take some time. Many block explorer offer API, but i doubt the free option is generous enough to let you get details of thousand address within short time. That site uses a captcha, look hard when opening using TOR. I tried opening that website on Tor Browser and didn't face any captcha or security check Another solution would be to host everything locally - full node, spv server like electrs and then rpc explorer.
Take note depending on which software you use, you only don't to run all 3. For example, Bcoin (full node with address index) or Bitcoin Core and Mempool.space. |
|
|
|
What do you think, folks?
I'll just add those member to ignore list, so i won't accidentally give them merit. |
|
|
|
--snip--
Not necessarily, we speak about the new members that join and stay arround. And for some reason the stats are terrible, if you put an average of how many users advance to the first rank, which is jr member, 20k users in 4 years is almost nothing. I get your point, although i'm not sure the stats is that terrible. After all, 78%/2.7 million account either have no post or banned (according to BPIP[1]). See cracked.io stats for example.
I found their statistic[2], but didn't find anything about "new members that join and stay around". [1] https://bpip.org/[2] https://cracked.io/statistics.php |
|
|
|
And on technical level, Brave still create unique browser fingerprint which could be used to track user.
I think you might be wrong about that, and you need to do more research about this, because brave is randomizing fingerprints each time. I am not sure how this works on their Tor window, and I am not endorsing Brave browser in any way, just correcting what you said. I decide to test this feature on my VM. As i expected, not all characteristic is randomized. Brave still send true resolution of the VM screen and time zone of the VM (not UTC). Besides. Brave also make these statement, Note that Private Windows with Tor Connectivity in Brave are just regular private windows that use Tor as a proxy. Brave does NOT implement most of the privacy protections from Tor Browser.
What if I want absolute anonymity while browsing?
If your personal safety depends on remaining anonymous, we highly recommend using Tor Browser instead of Brave Tor windows.
|
|
|
|
I'm in middle of trying alternative Bitcoin full node software which have function to verify sign message, so i decide to try it with few recent staked address. -----BEGIN BITCOIN SIGNED MESSAGE-----
Today is 13 Sept, 2022 and this is palle11 of BTT staking this address here as mine.
-----BEGIN SIGNATURE-----
17mtDab5mfK9rwup3UDmKCbaeHwuruFZKV
IN5zxE8FOEhF+ZgFSuILjaQxrgz0Wk8dbnJ8TmqqAC2wCt3JmzciX2hDm1DEhVNntMN9gg57TuwwrhREyObi7TQ=
-----END BITCOIN SIGNED MESSAGE-----
I have redone it with a legacy address from the same wallet and verified it on this site and it verified. Somebody should verify again to see if it completely verified. -----BEGIN BITCOIN SIGNED MESSAGE-----
Today 19/9/2022 I would like to sign my wallet from Electrum.
-----BEGIN SIGNATURE-----
bc1qaen0qmpw4j3lu83n7lzg6jncrgry7r7p0eplyl
Hz1Oiy3eXgwdUNsMxSKA/GJdx8XvDkY+4LrAP9k0yVkKb+OQOl/tMpBE7qU95N5rpR6ztGbCuKOBRnYxDGQ1J9k=
-----END BITCOIN SIGNED MESSAGE-----
Anyone can quote and verify my wallet Quoted and verified with Bcoin v2.2.0$ ./bcoin-cli --api-key=test_bcoin --http-port=48332 rpc verifymessage "17mtDab5mfK9rwup3UDmKCbaeHwuruFZKV" "IN5zxE8FOEhF+ZgFSuILjaQxrgz0Wk8dbnJ8TmqqAC2wCt3JmzciX2hDm1DEhVNntMN9gg57TuwwrhREyObi7TQ=" "Today is 13 Sept, 2022 and this is palle11 of BTT staking this address here as mine."
true
$ ./bcoin-cli --api-key=test_bcoin --http-port=48332 rpc verifymessage "bc1qaen0qmpw4j3lu83n7lzg6jncrgry7r7p0eplyl" "Hz1Oiy3eXgwdUNsMxSKA/GJdx8XvDkY+4LrAP9k0yVkKb+OQOl/tMpBE7qU95N5rpR6ztGbCuKOBRnYxDGQ1J9k=" "Today 19/9/2022 I would like to sign my wallet from Electrum."
true
|
|
|
|
However, has the same built-in checksum (a kind of hash) as the public version (v0.1.0) — Real checksum and built-in checksum do not match in the presented exe file — real checksum and built-in checksum match v0.1.0
It's good thing he and his worker have poor knowledge to manipulate binary file or proper programming knowledge to modify and recompile the source code. Unmodified built-in checksum is big giveaway for manipulation attempt. Repeated attempts to get a more detailed account of what happened to the private keys — because the story has changed several times over the years
This part is easy to understand and should be main argument why he's a big liar. Someone should find and make a list various story lie.
On a side note, i made archive request on archive.today for better backup diversity. https://archive.ph/6rr8jhttps://archive.ph/84Hmd |
|
|
|
|
Most exchange require few confirmation and high withdraw fee. If you frequently move your coin between exchange and hardware wallet, it's likely you'll lose your money either because,
1. You miss timing to make a sell/buy (due to amount of transaction confirmation).
2. You lose your profit due to high withdraw exchange fee.
3. You lose your profit due to transaction fee of that coin.
P.S. This reply was written for another member who might have similar question or visitor from google search result.
|
|
|
|
Thanks. It's possible that a block was corrupted due to unexpected exit of Bitcoin Core. While it quit automatically due to the abnormal condition, it's still a graceful exit as evident by having everything logged until the end. Yet it always happens when out of space, so evidently the cleanup isn't good. But it was on an older version. Maybe fixed in newer ones. I did quick search and few possible error/corruption due to out of storage space isn't fixed yet, https://github.com/bitcoin/bitcoin/issues/26112. That's just a note to mention which wallet is selected in the drop-down menu above it.
So it's sort of a bug or anti-feature in the case of non-wallet commands. I'd guess it's easier/faster to code function which show such message on all command. |
|
|
|
Do you know what's funny about this?  We could literally find 20 people in this forum who are willing to buy 7TB of HDD space to spin up BSV nodes and vote against Craig's 9 nodes. It would be great, just showing that it is this easy to attack a not properly decentralized blockchain. Are you by any chance one of those people?  It's pure waste of time and resources, but why not create such campaign, when he can spend all that time spreading toxicity and lawsuits worldwide. I am one of those people willing to do this experiment, yes!  You have read system requirement to run BSV node[1], right? To run node which can keep up with latest block, you need 8C/16T CPU, 64GB RAM and 100Mbit internet connection. I don't know how to find cheap VPS, but on Linode[2] it costs $320/month (Linode 64 GB shared CPU) + $200/month (10 TB S3 storage, unless you use prune mode). You might as well as burn your money. Who the hell is using BSV in 2022? Pump and dump altcoin traders?
Some time ago, certain weather app store their data on BSV blockchain[3]. [1] https://web.archive.org/web/20221009092610/https://node.bitcoinsv.io/sv-node/system-requirements[2] https://www.linode.com/pricing/[3] https://bitcoinist.com/96-of-bitcoin-sv-transactions-come-from-a-weather-app-report/ |
|
|
|
Whether it's leak or mandated by court, it's privacy disaster for all Celcius customer. --snip--
With regard to the withdrawals by executives, context is needed, and there is the potential for an explanation that is not scammy.
--snip--
I agree, although currently exit scam/other scam behavior is most probable guess. |
|
|
|
I don't plan to join the contest, but it'd be exciting to see how other participant carve their pumpkin. Prizes: 1st place receives everything shown below (plus more items to come, this is all I could get to easily today). --snip--  It'd be appreciated to mention security risks of using this hardware wallet. Personally i'd either use it as decoration or dissemble/terardown it for short review. |
|
|
|
After almost 4 days, i managed to mine 4 blocks. But due to relative slow internet connection, 2 of them become stale. Overall it's good experience and i got about ~0.05 tBTC, which probably will be used to try few different OPCODES on scripting or simply donate it to tBTC faucet. On a side note, on 3rd day i tried to mine only with 1 thread CPU since the goal to mine block with difficulty 1. But when i shutdown my PC, i got this error message with >100K occurrence. Quick search on google shows it's due continuous CPU usage for long time, although i'm not 100% sure it's due to bfgminer. kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P93622 } 116803 jiffies s: 7173 root: 0x1/.
kernel: rcu: blocking rcu_node structures (internal RCU debug): l=1:0-15:0x0/T
|
|
|
|
It appears Celsius has also made public a court document containing all their users' names, transaction times, and amounts of deposits and withdrawals. This is certainly a very serious breach of privacy.
And that document could be accessed at https://ia601401.us.archive.org/28/items/celsius/celsius.pdf. It has 277M size with total 14532 pages, which means you might have performance problem when opening that PDF file. I only spend few minute, but i saw coin transaction ranging to few cents to almost 1 million USD. I expect analytic company already parse this PDF as additional marketing data. |
|
|
|
If someone be able to predict your phrase than it can be easily hacked.
People can't simply predict your seed/recovery phrase. For 12 words length, there are 2048^12/16 possible combination permutation. In Trust wallet's case, we don't know that the seed phrases it generates are picked at random out of the 2048^12/16 possible permutations. That's true. I was just assuming Trust Wallet implement BIP39 correctly. As it's closed source, it's definitely possible that they create them deterministically and will either steal small amounts of funds (such that it goes unnoticed for as long as possible) or do a big giant rug pull in the future, emptying all of the wallets.
Not impossible, although i'd worry more about lack of privacy since they could collect and sell your data covertly. |
|
|
|
|
Show Posts
