Latest posts of: BlackHatCoiner

Show Posts
Pages: « 1 ... 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 [374] 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 ... 464 »

7461

Bitcoin / Bitcoin Technical Support / ThreadRPCServer incorrect password attempt from 127.0.0.1

on: May 02, 2021, 02:00:34 PM

Operating System: Ubuntu 18.04
Bitcoin Client: Bitcoin Core v0.21.0 release build.
Description of the problem: I run bitcoind with the parameters below and it works, but I then receive that "ThreadRPCServer incorrect password attempt from 127.0.0.1" error. It doesn't seem to change anything like stop working, but it just continuously returns it. What does it mean and how do I fix it?
Log file: https://pastebin.com/raw/Jbfq31Pw

Code:

angelo@angelocomputer:~/bitcoin/bin$ ./bitcoind -testnet -datadir=/media/angelo/1TB/p2p/BTC/AppData/testnet
2021-05-02T13:56:10Z Bitcoin Core version v0.21.0 (release build)
2021-05-02T13:56:10Z Assuming ancestors of block 000000000000006433d1efec504c53ca332b64963c425395515b01977bd7b3b0 have valid signatures.
2021-05-02T13:56:10Z Setting nMinimumChainWork=0000000000000000000000000000000000000000000001db6ec4ac88cf2272c6
2021-05-02T13:56:10Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2021-05-02T13:56:10Z Default data directory /home/angelo/.bitcoin
2021-05-02T13:56:10Z Using data directory /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3
2021-05-02T13:56:10Z Config file: /media/angelo/1TB/p2p/BTC/AppData/testnet/bitcoin.conf (not found, skipping)
2021-05-02T13:56:10Z Setting file arg: wallet = ["test"]
2021-05-02T13:56:10Z Command-line arg: datadir="/media/angelo/1TB/p2p/BTC/AppData/testnet"
2021-05-02T13:56:10Z Command-line arg: testnet=""
2021-05-02T13:56:10Z Using at most 125 automatic connections (1024 file descriptors available)
2021-05-02T13:56:10Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2021-05-02T13:56:10Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2021-05-02T13:56:10Z Script verification uses 1 additional threads
2021-05-02T13:56:10Z scheduler thread start
2021-05-02T13:56:10Z HTTP: creating work queue of depth 16
2021-05-02T13:56:10Z Using random cookie authentication.
2021-05-02T13:56:10Z Generated RPC authentication cookie /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/.cookie
2021-05-02T13:56:10Z HTTP: starting 4 worker threads
2021-05-02T13:56:10Z Using wallet directory /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/wallets
2021-05-02T13:56:10Z init message: Verifying wallet(s)...
2021-05-02T13:56:10Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2021-05-02T13:56:10Z Using wallet /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/wallets/test/wallet.dat
2021-05-02T13:56:10Z BerkeleyEnvironment::Open: LogDir=/media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/wallets/test/database ErrorFile=/media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/wallets/test/db.log
2021-05-02T13:56:10Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:12Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:12Z init message: Loading banlist...
2021-05-02T13:56:12Z SetNetworkActive: true
2021-05-02T13:56:12Z Using /16 prefix for IP bucketing
2021-05-02T13:56:12Z Cache configuration:
2021-05-02T13:56:12Z * Using 2.0 MiB for block index database
2021-05-02T13:56:12Z * Using 8.0 MiB for chain state database
2021-05-02T13:56:12Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2021-05-02T13:56:12Z init message: Loading block index...
2021-05-02T13:56:12Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
2021-05-02T13:56:12Z Opening LevelDB in /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/blocks/index
2021-05-02T13:56:12Z Opened LevelDB successfully
2021-05-02T13:56:12Z Using obfuscation key for /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/blocks/index: 0000000000000000
2021-05-02T13:56:16Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:16Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:20Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:20Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:24Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:24Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:26Z LoadBlockIndexDB: last block file = 197
2021-05-02T13:56:26Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1536, size=24551924, heights=1972270...1973835, time=2021-04-21...2021-05-02)
2021-05-02T13:56:26Z Checking all blk files are present...
2021-05-02T13:56:27Z Opening LevelDB in /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/chainstate
2021-05-02T13:56:27Z Opened LevelDB successfully
2021-05-02T13:56:27Z Using obfuscation key for /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/chainstate: 7c064d8c1f4992c5
2021-05-02T13:56:27Z Loaded best chain: hashBestChain=000000000000000597c6d123f53e04725afc19c3efce9cefcde56d21cba01db7 height=1973817 date=2021-05-02T12:30:14Z progress=0.999989
2021-05-02T13:56:27Z init message: Rewinding blocks...
2021-05-02T13:56:28Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) started
2021-05-02T13:56:28Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) completed (0.00s)
2021-05-02T13:56:28Z init message: Verifying blocks...
2021-05-02T13:56:28Z Verifying last 6 blocks at level 3
2021-05-02T13:56:28Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2021-05-02T13:56:28Z No coin database inconsistencies in last 6 blocks (65 transactions)
2021-05-02T13:56:28Z  block index           16661ms
2021-05-02T13:56:28Z init message: Loading wallet...
2021-05-02T13:56:28Z BerkeleyEnvironment::Open: LogDir=/media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/wallets/test/database ErrorFile=/media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/wallets/test/db.log
2021-05-02T13:56:29Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:29Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:29Z [test] Wallet File Version = 169900
2021-05-02T13:56:29Z [test] Keys: 2004 plaintext, 0 encrypted, 20004 w/ metadata, 2004 total. Unknown wallet records: 0
2021-05-02T13:56:30Z [test] Wallet completed loading in            1825ms
2021-05-02T13:56:30Z [test] setKeyPool.size() = 2000
2021-05-02T13:56:30Z [test] mapWallet.size() = 3
2021-05-02T13:56:30Z [test] m_address_book.size() = 6003
2021-05-02T13:56:30Z block tree size = 1973836
2021-05-02T13:56:30Z nBestHeight = 1973817
2021-05-02T13:56:30Z Bound to [::]:18333
2021-05-02T13:56:30Z torcontrol thread start
2021-05-02T13:56:30Z Bound to 0.0.0.0:18333
2021-05-02T13:56:30Z Bound to 127.0.0.1:18334
2021-05-02T13:56:30Z loadblk thread start
2021-05-02T13:56:30Z init message: Loading P2P addresses...
2021-05-02T13:56:30Z UpdateTip: new best=000000000000000ffface17e209b2223a6af32dbf8cd89899316ad5467bb546e height=1973818 version=0x27ffe000 log2_work=74.209103 tx=59974529 date='2021-05-02T12:39:31Z' progress=0.999991 cache=0.0MiB(66txo)
2021-05-02T13:56:30Z UpdateTip: new best=000000000000000d56571094d7cf071c0c37c73208109fdad037d36390a05cfb height=1973819 version=0x27ffe000 log2_work=74.209138 tx=59974530 date='2021-05-02T12:40:54Z' progress=0.999991 cache=0.0MiB(67txo)
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000002e5a4b5e28efa317ea2770697b4bce73a37b0141c72f37629 height=1973820 version=0x27ffe000 log2_work=74.209173 tx=59974537 date='2021-05-02T12:44:56Z' progress=0.999991 cache=0.0MiB(73txo)
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000000b9d317a7f4c61437b1594f021b442496f523ed234eb64d0d height=1973821 version=0x37ffe000 log2_work=74.209208 tx=59974541 date='2021-05-02T12:46:14Z' progress=0.999991 cache=0.0MiB(83txo)
2021-05-02T13:56:30Z UpdateTip: new best=00000000000000053ef79138eddddaffc49329da54c4917586dc69957f5472cc height=1973822 version=0x20e00000 log2_work=74.209243 tx=59974546 date='2021-05-02T12:49:45Z' progress=0.999992 cache=0.0MiB(97txo)
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000009b571e04159ce352ead96620f2001cb4c6c8e2db9709e39d9 height=1973823 version=0x37ffe000 log2_work=74.209278 tx=59974554 date='2021-05-02T12:52:55Z' progress=0.999992 cache=0.0MiB(107txo)
2021-05-02T13:56:30Z UpdateTip: new best=00000000000000226f9f493ad571350160511521c73b5fe4b01ef21a19f4a796 height=1973824 version=0x20800000 log2_work=74.209312 tx=59974557 date='2021-05-02T12:53:25Z' progress=0.999992 cache=0.0MiB(110txo)
2021-05-02T13:56:30Z UpdateTip: new best=000000000000001d927d04b24ec36301b3a4efcc2b453ebafce90f5babe1925f height=1973825 version=0x20c00000 log2_work=74.209347 tx=59974560 date='2021-05-02T12:55:49Z' progress=0.999993 cache=0.0MiB(116txo)
2021-05-02T13:56:30Z Loaded 18641 addresses from peers.dat  105ms
2021-05-02T13:56:30Z ERROR: DeserializeFileDB: Failed to open file /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/anchors.dat
2021-05-02T13:56:30Z 0 block-relay-only anchors will be tried for connections.
2021-05-02T13:56:30Z init message: Starting network threads...
2021-05-02T13:56:30Z net thread start
2021-05-02T13:56:30Z init message: Done loading
2021-05-02T13:56:30Z addcon thread start
2021-05-02T13:56:30Z dnsseed thread start
2021-05-02T13:56:30Z Waiting 300 seconds before querying DNS seeds.
2021-05-02T13:56:30Z opencon thread start
2021-05-02T13:56:30Z msghand thread start
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000015f1a8125022f28c020d4573ce58c77c5cd73f8509efdd1fa1 height=1973826 version=0x20800000 log2_work=74.209382 tx=59974695 date='2021-05-02T13:04:12Z' progress=0.999994 cache=0.1MiB(606txo)
2021-05-02T13:56:30Z UpdateTip: new best=000000000000001c4cb918c0b06f00f33b69a7d600885d451de7142b5abf7fd3 height=1973827 version=0x20000000 log2_work=74.209417 tx=59974699 date='2021-05-02T13:05:19Z' progress=0.999994 cache=0.1MiB(612txo)
2021-05-02T13:56:30Z UpdateTip: new best=00000000000000072a1136c1f984f34835ee9eebbbcee630a720afca06b407a3 height=1973828 version=0x20000000 log2_work=74.209452 tx=59974704 date='2021-05-02T13:05:56Z' progress=0.999994 cache=0.1MiB(622txo)
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000014f28c269d6f0ff73bbba4d4ae27363899e0820b67e31e7ad0 height=1973829 version=0x27ffe000 log2_work=74.209487 tx=59974731 date='2021-05-02T13:19:34Z' progress=0.999995 cache=0.1MiB(661txo)
2021-05-02T13:56:30Z UpdateTip: new best=00000000000000154c0d7a4834d24b8346b6c462eb5cfc25f9d9a2194f5cf9ed height=1973830 version=0x2fffe000 log2_work=74.209521 tx=59974740 date='2021-05-02T13:20:58Z' progress=0.999996 cache=0.1MiB(669txo)
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000003069fef9f960461e64de898fca9dad8b5c854d791fae0abfb height=1973831 version=0x20400000 log2_work=74.209556 tx=59974741 date='2021-05-02T13:21:04Z' progress=0.999996 cache=0.1MiB(670txo)
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000003bbdd8a679e303660070775ce8d90187dc01f3bce8baa0ea9 height=1973832 version=0x2fffe000 log2_work=74.209591 tx=59974748 date='2021-05-02T13:23:59Z' progress=0.999996 cache=0.1MiB(678txo)
2021-05-02T13:56:30Z UpdateTip: new best=00000000000000167fba394608a8fdb12f1b03fc999e8b6422fc37864e846887 height=1973833 version=0x20c00000 log2_work=74.209626 tx=59974754 date='2021-05-02T13:25:23Z' progress=0.999996 cache=0.1MiB(688txo)
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000001bb991be3ce9f24e1bbcb9debcbf6dcc29cc69b6bffc4c3dd height=1973834 version=0x20c00000 log2_work=74.209661 tx=59974756 date='2021-05-02T13:26:10Z' progress=0.999996 cache=0.1MiB(690txo)
2021-05-02T13:56:30Z UpdateTip: new best=00000000000000169c3b43824cd93cb787bb3ab88f89af4526efb8b878413866 height=1973835 version=0x20200000 log2_work=74.209695 tx=59974768 date='2021-05-02T13:31:44Z' progress=0.999997 cache=0.1MiB(704txo)
2021-05-02T13:56:30Z Imported mempool transactions from disk: 0 succeeded, 13 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2021-05-02T13:56:30Z loadblk thread exit
2021-05-02T13:56:31Z Leaving InitialBlockDownload (latching to false)
2021-05-02T13:56:31Z New outbound peer connected: version: 70015, blocks=1973839, peer=0 (full-relay)
2021-05-02T13:56:33Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:33Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:37Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:37Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:38Z UpdateTip: new best=0000000000000009d4be98b8d8ece34b91bc323e8395eb7b8fc88c469e1f1584 height=1973836 version=0x27ffe000 log2_work=74.209730 tx=59974790 date='2021-05-02T13:43:24Z' progress=0.999998 cache=0.1MiB(736txo)
2021-05-02T13:56:38Z UpdateTip: new best=0000000000000013bcf985eaebc79e5599c28ab4adb3b931cb92499a3cfa5272 height=1973837 version=0x20000000 log2_work=74.209765 tx=59974796 date='2021-05-02T13:46:59Z' progress=0.999999 cache=0.1MiB(739txo)
2021-05-02T13:56:38Z UpdateTip: new best=0000000000000011338bdf80cd11484c2522ed38978d6806750585d216bcc46d height=1973838 version=0x20c00000 log2_work=74.209800 tx=59974799 date='2021-05-02T13:49:11Z' progress=0.999999 cache=0.1MiB(744txo)
2021-05-02T13:56:38Z UpdateTip: new best=0000000000000009080fa46b471b908099d8cc849f02774ac372e114c4cd9571 height=1973839 version=0x2fffe000 log2_work=74.209835 tx=59974825 date='2021-05-02T13:55:50Z' progress=1.000000 cache=0.1MiB(770txo)
2021-05-02T13:56:41Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:41Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:43Z New outbound peer connected: version: 70016, blocks=1973839, peer=1 (full-relay)
2021-05-02T13:56:44Z New outbound peer connected: version: 70015, blocks=1973839, peer=2 (full-relay)
2021-05-02T13:56:45Z New outbound peer connected: version: 70015, blocks=1973839, peer=3 (full-relay)
2021-05-02T13:56:45Z New outbound peer connected: version: 70016, blocks=1973839, peer=4 (full-relay)
2021-05-02T13:56:46Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:46Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438

bitcoin.conf:

Code:

server=1
listen=1
daemon=1
txindex=1
rpcallowip=127.0.0.1

7462

Bitcoin / Development & Technical Discussion / Re: How to create millions of Bitcoin addresses

on: May 02, 2021, 01:34:34 PM

Quote from: 0x77 on April 30, 2021, 08:06:46 AM Are there ideas and solutions? Not sure what exactly you want, but you can derive millions of Bitcoin addresses from one master public key. Check iancoleman to see how it works. Loading the balances of millions of addresses won't work if you rely on third parties. You'll have to run your own Bitcoin node for sure. If you're keen on using electrum here's a nice way to achieve what you want: Electrum Personal Server. Quote from: ETFbitcoin on May 01, 2021, 09:41:58 AM Not best option, because 1. Electrum wallet isn't scalable (one of the reason is usage of JSON to store the information). 2. Electrum server maximum request for each user. Can you analyze the first reason a little bit more? Besides the above, he'll expose all these addresses to electrum nodes, which isn't recommended for privacy reasons, especially if they're clients' addresses.

7463

Bitcoin / Electrum / Re: [Questions] Running my own electrum server

on: May 02, 2021, 01:20:53 PM

Quote from: ETFbitcoin on May 02, 2021, 08:54:49 AM If you see message "Hello from Docker!", then Docker run correctly. On the WSL I don't get it. I returns me an error instead. But don't worry, I'll setup it on my Ubuntu machine. On my Ubuntu 18.04 the hello-world works properly, but not the script you've given: Quote from: Trechometer on May 02, 2021, 09:53:42 AM Please share some more informations, I also wanted to start with electrum, but failed to install and run. Lets help us each other if you are also at the beginning. If you read the entire thread, you'll find the information you're searching. In a few words, I'm fumbled with the whole server thing... . I feel better now that I see that I am not the only one with these issues. Quote from: Trechometer on May 02, 2021, 09:53:42 AM And the VPS is hardware or software or rented? I think it's software, but I ain't completely sure. It's really cheap so I doubt if it'd be a hardware one.

7464

Bitcoin / Development & Technical Discussion / Re: The consensus dead end.

on: May 01, 2021, 08:14:13 PM

Quote from: Metal Brain on May 01, 2021, 07:46:36 PM There must be a downside or everybody would use the lightning network. It adds an extra level of complication for the average user (IMO) and it is accepted by dramatically few stores. These are the only disadvantages I observe with LN. It's under development, but it's being implemented. Here's some nice links to watch: Basics of the Lightning Network The Lightning Network FAQ Electrum Lightning Network walkthrough_{(if you're using electrum)} I'd please you, now, to stop double posting and derailing this thread with posts related to forks of Bitcoin. The main topic of this thread is the consensus' future, or as I call it, the dead end. We've already gone way too off-topic. You're free to create a thread explaining why Bitcoin Cash is a better option than Bitcoin.

7465

Bitcoin / Development & Technical Discussion / Re: The consensus dead end.

on: May 01, 2021, 07:21:27 PM

Quote from: Metal Brain on May 01, 2021, 06:17:43 PM Black hat said at least $5 transaction fee for $100. Would you mind quoting me, to see where exactly did I say that? Quote from: Metal Brain on May 01, 2021, 06:17:43 PM If there is an exception he omitted he should own up to it and provide that source of information instead of pretending he gave me a different figure. Everyone can pay 1 satoshi for an off-chain transaction, as long as they'll pay two on-chain transactions for opening and closing a channel. This means that unlimited transactions between two parties can be made, by only broadcasting two transcations. And it gets better! Lightning nodes can connect with each other forming a network of users that transact off-chainly. Not strictly to two parties!

7466

Bitcoin / Development & Technical Discussion / Re: The consensus dead end.

on: May 01, 2021, 06:04:44 PM

Quote from: Metal Brain on May 01, 2021, 05:50:46 PM Black hat told me different. “Black hat” had also told you to read what is the Lightning Network. Did you?

7467

Bitcoin / Development & Technical Discussion / Re: The consensus dead end.

on: May 01, 2021, 05:07:30 PM

Quote from: Metal Brain on May 01, 2021, 05:01:56 PM All that matters here is how much it is going to cost you above that $100 to make the transaction to a foreign country. I think I paid about a 3% fee to Mastercard because it was a foreign country. I once paid 1 satoshi for a LN transaction oversea. One! Can you do this with Mastercard?

7468

Bitcoin / Development & Technical Discussion / Re: 51 Node attack

on: May 01, 2021, 04:41:59 PM

Quote from: Qosmos_81 on May 01, 2021, 04:27:02 PM If i understand it correct nodes check transactions if thy are valid. if some node doesnt follow the rules , it got kicked from the network. A node that doesn't accept the consensus rules is simply not accepted from other nodes. Just like a Litecoin node isn't accepted from a Bitcoin node. They both follow different rules. Quote from: Qosmos_81 on May 01, 2021, 04:27:02 PM But if some party owns 51 % of the nodes, can they change the rules ? can they accept false transactions? There's hereby a possible misunderstanding of how a node works. If you're running a Bitcoin node, you are following some hard-coded consensus rules and at the same time, you're receiving blocks. The blocks you're receiving aren't “gulped” from your node. It verifies every single block it receives to see if it's valid according to the consensus rules it follows. The entire Bitcoin network is made up of nodes making their own decisions, but they each make the same decisions as one another. That being said, a 51% node attack doesn't hold water. Quote from: Qosmos_81 on May 01, 2021, 04:27:02 PM Or Can they only make a hardfork because they dont follow the rules anymore? A hard fork can be created from anyone. You don't have to be the owner of those 51%.

7469

Bitcoin / Bitcoin Discussion / Re: travelling internationally with a hard wallet

on: May 01, 2021, 04:28:50 PM

@jakesun64, I'm sure that you'll be fine, but even if you want to be hundred percent sure for your safety on your international traveling, then simply: Don't use hardware wallets. Use a computer software instead. There are plenty of useful non-custodial wallets. My favourites are electrum and wasabi. Although, you must ensure that the laptop you're travelling doesn't contain anything malicious. Keep in mind that the difference with software wallets is that your keys can be found on your hard drive. If you're not sure about your computer's security ^{(you are probably not)}, don't risk your funds. Carry the device with you. Quote from: Coin_trader on May 01, 2021, 01:57:09 PM If you are that conscious about carrying hardware wallet. Why not use crypto visa card like Crypto.com or Swipe wallet card. You can still store your crypto on your visa card without worrying that airport personnel will deny you during luggage checking. How can you really propose such solution to someone? Since when storing your bitcoins on a hardware wallet is the same thing with visa card or any other single authority? Quote from: Poker Player on May 01, 2021, 03:49:04 PM But wouldn't it be better to transfer part of your funds to a wallet on your mobile, uninstall it and install it again when you arrive at your destination? No, it wouldn't. You would then have to trust your mobile, which usually runs on a closed-source environment. Besides the operating system, you have to be careful of the apk you'll install. Not to mention that you have to be sure about your phone's security. There are just so many victims that lost funds from a mobile wallet... That's because there are many intermediates. A person that isn't familiar with technology will have to trust: The operating system's developers. The developer of the wallet. The app store he/she will download it from. Every other application he/she has installed.

7470

Bitcoin / Electrum / Re: [Questions] Running my own electrum server

on: May 01, 2021, 11:27:40 AM

Quote from: ETFbitcoin on May 01, 2021, 09:47:00 AM Honestly if the VPS use linux, you can use easy installer/docker (which i mentioned above), which is very easy to use. I saw the docker, but I haven't ever used docker in the past for setups. Would you mind guiding me a hand? There's no steps, just a “`docker run /`” script.

7471

Bitcoin / Development & Technical Discussion / Re: 10 minutes block interval and network modelling

on: April 30, 2021, 09:05:13 PM

Quote from: zeuner on April 30, 2021, 06:56:33 PM Who says a blockchain with a lower block interval would necessarily use the same block size? A comparison might be more meaningful if the average block storage size per hour is kept constant. If you reduced the block size, why would you change the block interval in the first place?

7472

Bitcoin / Development & Technical Discussion / Re: The consensus dead end.

on: April 30, 2021, 05:08:31 PM

I don't have anything to respond you. It seems that you're prejudiced about Bitcoin and Bitcoin Cash. Although, I'll have to inform you that there's something unique on Bitcoin. That something is what makes it special and different from any other cryptocurrency. It has everyone's agreement.

7473

Bitcoin / Electrum / Re: [Questions] Running my own electrum server

on: April 30, 2021, 12:53:51 PM

Quote from: HCP on April 30, 2021, 08:59:51 AM oh man... if I had known you just wanted a little local Electrum server... I would have recommended electrs I thought you were trying to get your own public facing Electrum server up and running. I do. I just wanted to firstly setup a personal server. Running a server publicly is secondary. Quote from: ETFbitcoin on April 30, 2021, 09:42:58 AM 3. Setup with systemd, https://electrumx-spesmilo.readthedocs.io/en/latest/HOWTO.html#using-systemd The problem with electrumx is that I still haven't understood how it works. For example, on electrum-personal-server, you're starting the server with `electrum-personal-server config.ini`. With what file do you start electrumx? `service/electrumx`? The tutorial doesn't tell you much. It just says "run that command, then another command etc.". Where's the explanation? How am I supposed to know what does that do and from what directory should I run it?: Code: systemctl start electrumx This is what it returns me when I execute the above command: Code: angelo@angelopc:~/Desktop/electrumx$ systemctl start electrumx Warning: The unit file, source configuration file or drop-ins of electrumx.service changed on disk. Run 'systemctl daemon-reload' to reload units. Job for electrumx.service failed because of unavailable resources or another system error. See "systemctl status electrumx.service" and "journalctl -xe" for details. And then with `systemctl status electrumx.service` (as it's been said in the error): Code: angelo@angelopc:~/Desktop$ systemctl status electrumx.service ● electrumx.service - Electrumx Loaded: loaded (/etc/systemd/system/electrumx.service; disabled; vendor prese Active: failed (Result: resources) Απρ 30 15:21:48 angelopc systemd[1]: electrumx.service: Failed with result 'reso Απρ 30 15:21:48 angelopc systemd[1]: Failed to start Electrumx. Απρ 30 15:21:53 angelopc systemd[1]: electrumx.service: Failed to load environme Απρ 30 15:21:53 angelopc systemd[1]: electrumx.service: Failed to run 'start' ta Απρ 30 15:21:53 angelopc systemd[1]: electrumx.service: Failed with result 'reso Απρ 30 15:21:53 angelopc systemd[1]: Failed to start Electrumx. Απρ 30 15:22:14 angelopc systemd[1]: electrumx.service: Failed to load environme Απρ 30 15:22:14 angelopc systemd[1]: electrumx.service: Failed to run 'start' ta Απρ 30 15:22:14 angelopc systemd[1]: electrumx.service: Failed with result 'reso Απρ 30 15:22:14 angelopc systemd[1]: Failed to start Electrumx. (Απρ is Apr on my lang) As I said, I have a VPS left over and I'd like to "donate" its operation to the electrum community instead of having it shut down. I also like practicing in this field. I'd have probably given up with this setup, but it seems that I'm a stubborn...

7474

Bitcoin / Development & Technical Discussion / Re: 10 minutes block interval and network modelling

on: April 30, 2021, 11:10:52 AM

Quote from: baro77 on April 30, 2021, 10:36:18 AM I mean: going on, storage costs seem to become cheaper at a faster rate than computational power and network speed.... Sure, it does. Terabytes back in 2009 were much more expensive than today. He/she may failed to predict the future. Quote from: baro77 on April 30, 2021, 10:36:18 AM 1) it cannot be a general solution, full node are a strict need of the network (btw, if it could be a general solution, needed-storage growth would be even less important effect to take into account while choosing the block time interval) Did I say to reduce the bandwidth? Sorry, I meant the storage. The bandwidth remains the same whether you're running pruned or not pruned. Yes, full nodes are required for the network in contrast with pruned ones. Here's some food for thought questions: 1) Do pruned nodes allow incoming connections? If yes, why? They shouldn't be sharing anything, only validating the chain. 2) What happens to pruned nodes on a 51% attack? Quote from: baro77 on April 30, 2021, 10:36:18 AM 2) I believe (correct me if I'm wrong) that it doesn't reduce the IBD, so neither benefit from the point of view of nework speed No, I didn't mean the network speed. I meant the bandwidth of each node. The process to share each one's blocks. If the interval was 2 minutes, the bandwidth required would be 5x than now.

7475

Bitcoin / Development & Technical Discussion / Re: 10 minutes block interval and network modelling

on: April 30, 2021, 09:57:52 AM

Well, we're definitely not 100% sure for this decision. Satoshi may chose it, because of the calculations he/she had done. Giving that a block can be 1MB max size, it'd mean that every 52,500 blocks (~1 year), the chain would weight up to 52.5GB more than it did a year ago. Back in 2009, I'm not sure how big was this. In the whitepaper, he/she mentioned about pruning the chain instead of keeping it, though. I guess that he/she did this to reduce the bandwidth between the nodes and to reduce chain's size. If every block was solved every 2 minutes averagely (which is a satisfying interval for the user), the block chain would weight more than 2TB and thus, there'd be fewer nodes. The number ten was probably a round-assumption and not a well-thought. You can't really pick a round number and believe that it'll be the best case for both sides.

7476

Bitcoin / Electrum / Re: [Questions] Running my own electrum server

on: April 30, 2021, 08:42:37 AM

I didn't fix it. I don't know why it didn't work, but I was feeling a little alienated after all those tries. I then watched a video on YouTube which was much more simpler than with electrumx's tutorial. Thus, I discovered electrum personal server which seems a great implementation under some serious development. So, I just switched to EPS. I didn't fix electrumx. I may formulated it wrongly, but "fixed" goes to my main purpose, which is running electrum without trusting anyone. I achieved it, thank you for your help.

7477

Bitcoin / Development & Technical Discussion / Re: Authorization failed: Incorrect rpcuser or rpcpassword

on: April 29, 2021, 06:24:24 PM

Quote from: NotATether on April 29, 2021, 06:10:19 PM Instead of `--rpcuser=test123456 --rpcpassword=123456`, write `--rpcuser=__cookie__ --rpcpassword=<long hex string inside the .cookie file>` and remove the stuff from your config file since the .cookie file is autogenerated at runtime. Yes, it works! Thank you.

7478

Bitcoin / Development & Technical Discussion / Re: Authorization failed: Incorrect rpcuser or rpcpassword

on: April 29, 2021, 05:26:14 PM

Quote from: NotATether on April 29, 2021, 05:15:13 PM If you use the password in the .cookie file instead of writing your password on the command line Use it where and how?

7479

Bitcoin / Development & Technical Discussion / Authorization failed: Incorrect rpcuser or rpcpassword

on: April 29, 2021, 05:02:43 PM

For some reason, once I enter the following command on the terminal I get this error: Code: angelo@angelopc:~/Desktop/bitcoin/bin$ ./bitcoin-cli --testnet --rpcuser=test123456 --rpcpassword=123456 --netinfo error: Authorization failed: Incorrect rpcuser or rpcpassword The thing is that these are the correct credentials, I haven't made any mistakes. Here's my bitcoin.conf: Code: server=1 listen=1 daemon=1 txindex=1 rpcuser=test123456 rpcpassword=123456 What is going on? FYI, the configuration file is located on an external drive, while the binaries of Bitcoin Core are on my internal SSD.

7480

Bitcoin / Electrum / Re: [Questions] Running my own electrum server

on: April 29, 2021, 12:28:25 PM

Thank you for your time! Quote from: ETFbitcoin on April 29, 2021, 12:02:22 PM 9. Start svscan If you can't have multiple terminal run this instead Code: cd /home/user/Desktop/electrumx svscan ./service & disown ~~I have an issue with svscan~~ Fixed. I'm now running electrum-personal-server.

Pages: « 1 ... 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 [374] 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 ... 464 »