Ninjastic
Search content
Sort by
Showing 10 of 10 results by Bitcoiner317
Post
Topic
Board Bitcoin Discussion
Merits 1 from 1 user
Topic OP
Bitcoin forks and ETFs
by
Bitcoiner317
on 23/05/2024, 14:04:53 UTC
⭐ Merited by ABCbits (1)
As I was thinking about the whole debate on ordinals and segwit, it had me wonder.

Forks might still happen in the future of Bitcoin. When you own your coins, you're sort of protected financially in the sense that you now own coins on both networks and will still be on the train whether a chain or another keeps traction as the other loses popularity. When you own shares of a Bitcoin ETF, you don't get to choose what path you want to take and if the community decides the new fork is the way to go.. I doubt the financial institution would take the risk of switching networks.

With all the hassle it seems to be to get an ETF approved, do you think financial institution would go through the hassle of giving their share holders their owned value of the second chain? How would that work exactly? And most importantly, doesn't that mean that the more ETFs gain traction, the more the original chain would keep its value over the other one? Since tradfi got in the game, it kinda gives an unfair advantage to pre-fork bitcoin chain.

What are your thoughts on this?
Post
Topic
Board Bitcoin Discussion
Re: One reason why bitcoin is still the King
by
Bitcoiner317
on 18/02/2023, 04:28:42 UTC
Ugh. Read the room.

I cam here to read good talks about the technological and sociological impacts of Bitcoin. Not moonboys shitposts about crypto prices. I’m sorry if this comes out wrong, I just got here. But BTC isn’t even comparable to other "coins" and I feel like most bitcoiners don’t really care about price that much. Correct me if I’m wrong.

Of course gains led most of us to where we are today but the deep dive into everything gravitating around bitcoin is enough, at least personally, to be able to save in BTC without looking back. Its freedom is largely worth it.
Post
Topic
Board Bitcoin Discussion
Re: On Ordinals: Where do you stand?
by
Bitcoiner317
on 13/02/2023, 18:16:46 UTC
Shouldn’t miners’ revenue go up with all this ordeal? I’m confused.

https://ycharts.com/indicators/bitcoin_miners_revenue_per_day
Post
Topic
Board Bitcoin Discussion
Re: On Ordinals: Where do you stand?
by
Bitcoiner317
on 10/02/2023, 23:19:50 UTC
Thanks for the summary. Well, this is disappointing to say the least.
I guess it’s unavoidable for some people to want to take control when a decentralized system of that scale happens to be within reach. Guess we’ll have to watch them closely, haha
Post
Topic
Board Bitcoin Technical Support
Re: Node unactive? Blocks stuck at 97%
by
Bitcoiner317
on 10/02/2023, 22:24:14 UTC
Alright so I managed to get TOR up and running (glad I had the node issue cause I wouldn't have realized it wasn't running). Core still wouldn't connect to any peer for some reason so I decided to hash out onlynet=onion and it's working now.
Post
Topic
Board Bitcoin Discussion
Re: On Ordinals: Where do you stand?
by
Bitcoiner317
on 10/02/2023, 13:40:19 UTC
Quote from: franky1 on Today at 01:01:48 PM
other options are
taproot devs made a promise that taproot witness would look like a single signature of <80bytes
and so keeping to that promise they can release a client we all upgrade to. that from block 7xx,xxx all taproots relayed at unconfirm are only 80byte limit witness. and if they get into a block after 7xx,xxx they would reject a block that breaks the rule

That's great and all but no action will be taken if the community is censored. Do we need to send a petition to the Devs or somethings?  :lol:
Post
Topic
Board Bitcoin Discussion
Re: On Ordinals: Where do you stand?
by
Bitcoiner317
on 10/02/2023, 12:30:33 UTC
There’s so many people complaining about this
That I don’t understand why no action is being taken. Is our only course of action just really downgrading core hoping others do the same?
Post
Topic
Board Bitcoin Technical Support
Re: Node unactive? Blocks stuck at 97%
by
Bitcoiner317
on 09/02/2023, 13:12:32 UTC
Quote from: nc50lc on Today at 07:21:56 AM
Probably not related to the issue but you have a typo in your config:

Thanks!

Quote from: NotATether on Today at 11:25:31 AM
Check if your proxy is down. You're using only Tor, so make sure you can still connect to that.

When listing system services, it seems tor.service is active but tor@default.service returned as loaded but FAILED.
But I can't seem to figure out what went wrong..
I get the following under journalctl -xeu tor@default.service

Quote
Feb 09 07:51:35 Anonymous-Laptop systemd[1]: Failed to start Anonymizing overlay network for TCP.

And the following under sudo journalctl -u tor@default.service


Quote
Jan 02 22:32:30 Anonymous-Laptop systemd[1]: Starting Anonymizing overlay network for TCP...
Jan 02 22:32:30 Anonymous-Laptop tor[4845]: Jan 02 22:32:30.572 [notice] Tor 0.4.6.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc.
Jan 02 22:32:30 Anonymous-Laptop tor[4845]: Jan 02 22:32:30.573 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jan 02 22:32:30 Anonymous-Laptop tor[4845]: Jan 02 22:32:30.573 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Jan 02 22:32:30 Anonymous-Laptop tor[4845]: Jan 02 22:32:30.574 [notice] Read configuration file "/etc/tor/torrc".
Jan 02 22:32:30 Anonymous-Laptop tor[4845]: Configuration was valid
Jan 02 22:32:30 Anonymous-Laptop tor[4854]: Jan 02 22:32:30.778 [notice] Tor 0.4.6.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc.
Jan 02 22:32:30 Anonymous-Laptop tor[4854]: Jan 02 22:32:30.778 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jan 02 22:32:30 Anonymous-Laptop tor[4854]: Jan 02 22:32:30.778 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Jan 02 22:32:30 Anonymous-Laptop tor[4854]: Jan 02 22:32:30.778 [notice] Read configuration file "/etc/tor/torrc".
Jan 02 22:32:30 Anonymous-Laptop tor[4854]: Jan 02 22:32:30.785 [notice] Opening Socks listener on 127.0.0.1:9050
Jan 02 22:32:30 Anonymous-Laptop tor[4854]: Jan 02 22:32:30.785 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: We compiled with OpenSSL 30000020: OpenSSL 3.0.2 15 Mar 2022 and we are running with OpenSSL 30000020: 3.0.2. These two versions should be binary compatible.
Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: Tor 0.4.6.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc.
Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: Read configuration file "/etc/tor/torrc".
Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: Opening Socks listener on 127.0.0.1:9050
Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: Opened Socks listener connection (ready) on 127.0.0.1:9050
Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Jan 02 22:32:31 Anonymous-Laptop Tor[4854]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Post
Topic
Board Bitcoin Discussion
Merits 2 from 2 users
Re: On Ordinals: Where do you stand?
by
Bitcoiner317
on 09/02/2023, 11:47:05 UTC
⭐ Merited by NotATether (1) ,ETFbitcoin (1)
Time will tell in my opinion. It’s a slippery slope for sure. I wish this wouldn’t have been possible without a hard fork, because now most people will probably just go with it. I am against NFTs on mainchain, that’s for sure. But for now, fees remain unaffected and block size has risen only to the recent hype of ordinals. One can hope for the fad to pass and bloat to be released. IMO, blocks should remain as lean as possible. But the possibility to add more date to the chain could open new possibilities for feature on second layers.

Post
Topic
Board Bitcoin Technical Support
Merits 4 from 2 users
Topic OP
Node unactive? Blocks stuck at 97%
by
Bitcoiner317
on 09/02/2023, 03:20:56 UTC
⭐ Merited by hugeblack (3) ,ETFbitcoin (1)
I'm not too sure what I've done wrong. The node used to run fine but I've been experimenting with Ubuntu and new blocks aren't loading anymore. Might be due to updating my node from core v22 to v24. Anyway - can anybody spot a clue? Would be much appreciated! It seems like I'm not getting any connections for some reason.

bitcoin.conf:

   
Code:
datadir=/media/anonymous/T7/Bitcoin/
   
    # Needed for full validation
    addumevalid=0
   
    #not needed but will show useful info later
    #debug=net
   
    server=1
    txindex=1
    daemon=1
    rpcport=8332
    rpcbind=0.0.0.0
    rpcallowip=127.0.0.1
    rpcallowip=10.0.0.0/8
    rpcallowip=172.0.0.0/8
    rpcallowip=192.0.0.0/8
    zmqpubrawblock=tcp://0.0.0.0:28332
    zmqpubrawtx=tcp://0.0.0.0:28333
    zmqpubhashblock=tcp://0.0.0.0:28334
    whitelist=127.0.0.1
    rpcauth=****
   
    proxy=127.0.0.1:9050
    listen=1
    bind=127.0.0.1
    onlynet=onion

debug.log:
Code:
    2023-02-09T02:34:22Z Ignoring unknown configuration value addumevalid
    2023-02-09T02:34:22Z Bitcoin Core version v24.0.1 (release build)
    2023-02-09T02:34:22Z InitParameterInteraction: parameter interaction: -proxy set -> setting -upnp=0
    2023-02-09T02:34:22Z InitParameterInteraction: parameter interaction: -proxy set -> setting -natpmp=0
    2023-02-09T02:34:22Z InitParameterInteraction: parameter interaction: -proxy set -> setting -discover=0
    2023-02-09T02:34:22Z InitParameterInteraction: parameter interaction: -onlynet excludes IPv4 and IPv6 -> setting -dnsseed=0
    2023-02-09T02:34:22Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
    2023-02-09T02:34:22Z Default data directory /home/anonymous/.bitcoin
    2023-02-09T02:34:22Z Using data directory /media/anonymous/T7/Bitcoin
    2023-02-09T02:34:22Z Config file: /home/anonymous/.bitcoin/bitcoin.conf
    2023-02-09T02:34:22Z Config file arg: bind="127.0.0.1"
    2023-02-09T02:34:22Z Config file arg: daemon="1"
    2023-02-09T02:34:22Z Config file arg: datadir="/media/anonymous/T7/Bitcoin/"
    2023-02-09T02:34:22Z Config file arg: listen="1"
    2023-02-09T02:34:22Z Config file arg: onlynet="onion"
    2023-02-09T02:34:22Z Config file arg: proxy="127.0.0.1:9050"
    2023-02-09T02:34:22Z Config file arg: rpcallowip="127.0.0.1"
    2023-02-09T02:34:22Z Config file arg: rpcallowip="10.0.0.0/8"
    2023-02-09T02:34:22Z Config file arg: rpcallowip="172.0.0.0/8"
    2023-02-09T02:34:22Z Config file arg: rpcallowip="192.0.0.0/8"
    2023-02-09T02:34:22Z Config file arg: rpcauth=****
    2023-02-09T02:34:22Z Config file arg: rpcbind=****
    2023-02-09T02:34:22Z Config file arg: rpcport="8332"
    2023-02-09T02:34:22Z Config file arg: server="1"
    2023-02-09T02:34:22Z Config file arg: txindex="1"
    2023-02-09T02:34:22Z Config file arg: whitelist="127.0.0.1"
    2023-02-09T02:34:22Z Config file arg: zmqpubhashblock="tcp://0.0.0.0:28334"
    2023-02-09T02:34:22Z Config file arg: zmqpubrawblock="tcp://0.0.0.0:28332"
    2023-02-09T02:34:22Z Config file arg: zmqpubrawtx="tcp://0.0.0.0:28333"
    2023-02-09T02:34:22Z Command-line arg: conf="/home/anonymous/.bitcoin/bitcoin.conf"
    2023-02-09T02:34:22Z Command-line arg: daemon=""
    2023-02-09T02:34:22Z Command-line arg: datadir="/media/anonymous/T7/Bitcoin"
    2023-02-09T02:34:22Z Command-line arg: pid="/media/anonymous/T7/Bitcoin/bitcoind.pid"
    2023-02-09T02:34:22Z Using at most 125 automatic connections (1024 file descriptors available)
    2023-02-09T02:34:23Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
    2023-02-09T02:34:23Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
    2023-02-09T02:34:23Z Script verification uses 3 additional threads
    2023-02-09T02:34:23Z scheduler thread start
    2023-02-09T02:34:23Z WARNING: the RPC server is not safe to expose to untrusted networks such as the public internet
    2023-02-09T02:34:23Z [http] creating work queue of depth 16
    2023-02-09T02:34:23Z Using random cookie authentication.
    2023-02-09T02:34:23Z Generated RPC authentication cookie /media/anonymous/T7/Bitcoin/.cookie
    2023-02-09T02:34:23Z Using rpcauth authentication.
    2023-02-09T02:34:23Z [http] starting 4 worker threads
    2023-02-09T02:34:23Z Using wallet directory /media/anonymous/T7/Bitcoin
    2023-02-09T02:34:23Z init message: Verifying wallet(s)…
    2023-02-09T02:34:23Z Using /16 prefix for IP bucketing
    2023-02-09T02:34:23Z init message: Loading P2P addresses…
    2023-02-09T02:34:23Z Loaded 57414 addresses from peers.dat  608ms
    2023-02-09T02:34:23Z init message: Loading banlist…
    2023-02-09T02:34:23Z SetNetworkActive: true
    2023-02-09T02:34:23Z Cache configuration:
    2023-02-09T02:34:23Z * Using 2.0 MiB for block index database
    2023-02-09T02:34:23Z * Using 56.0 MiB for transaction index database
    2023-02-09T02:34:23Z * Using 8.0 MiB for chain state database
    2023-02-09T02:34:23Z * Using 384.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
    2023-02-09T02:34:23Z init message: Loading block index…
    2023-02-09T02:34:23Z Assuming ancestors of block 00000000000000000009c97098b5295f7e5f183ac811fb5d1534040adb93cabd have valid signatures.
    2023-02-09T02:34:23Z Setting nMinimumChainWork=00000000000000000000000000000000000000003404ba0801921119f903495e
    2023-02-09T02:34:23Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
    2023-02-09T02:34:23Z Opening LevelDB in /media/anonymous/T7/Bitcoin/blocks/index
    2023-02-09T02:34:23Z Opened LevelDB successfully
    2023-02-09T02:34:23Z Using obfuscation key for /media/anonymous/T7/Bitcoin/blocks/index: 0000000000000000
    2023-02-09T02:34:33Z LoadBlockIndexDB: last block file = 3277
    2023-02-09T02:34:33Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=61, size=76919772, heights=763336...763446, time=2022-11-15...2022-11-16)
    2023-02-09T02:34:33Z Checking all blk files are present...
    2023-02-09T02:34:36Z Opening LevelDB in /media/anonymous/T7/Bitcoin/chainstate
    2023-02-09T02:34:36Z Opened LevelDB successfully
    2023-02-09T02:34:36Z Using obfuscation key for /media/anonymous/T7/Bitcoin/chainstate: 26573160958bad91
    2023-02-09T02:34:36Z Loaded best chain: hashBestChain=00000000000000000004698262d70574cdfe6f8fbfa9f09f3289163c2d8c0c29 height=763398 date=2022-11-16T08:10:57Z progress=0.973287
    2023-02-09T02:34:36Z init message: Verifying blocks…
    2023-02-09T02:34:36Z Verifying last 6 blocks at level 3
    2023-02-09T02:34:36Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
    2023-02-09T02:34:38Z No coin database inconsistencies in last 6 blocks (8457 transactions)
    2023-02-09T02:34:38Z  block index           14704ms
    2023-02-09T02:34:38Z Opening LevelDB in /media/anonymous/T7/Bitcoin/indexes/txindex
    2023-02-09T02:34:39Z Opened LevelDB successfully
    2023-02-09T02:34:39Z Using obfuscation key for /media/anonymous/T7/Bitcoin/indexes/txindex: 0000000000000000
    2023-02-09T02:34:39Z Setting NODE_NETWORK on non-prune mode
    2023-02-09T02:34:39Z txindex thread start
    2023-02-09T02:34:39Z txindex is enabled at height 763398
    2023-02-09T02:34:39Z txindex thread exit
    2023-02-09T02:34:39Z loadblk thread start
    2023-02-09T02:34:39Z block tree size = 770107
    2023-02-09T02:34:39Z nBestHeight = 763398
    2023-02-09T02:34:39Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
    2023-02-09T02:34:39Z loadblk thread exit
    2023-02-09T02:34:39Z torcontrol thread start
    2023-02-09T02:34:39Z Bound to 127.0.0.1:8333
    2023-02-09T02:34:39Z Bound to 127.0.0.1:8334
    2023-02-09T02:34:39Z Loaded 0 addresses from "anchors.dat"
    2023-02-09T02:34:39Z 0 block-relay-only anchors will be tried for connections.
    2023-02-09T02:34:39Z init message: Starting network threads…
    2023-02-09T02:34:39Z DNS seeding disabled
    2023-02-09T02:34:39Z net thread start
    2023-02-09T02:34:39Z addcon thread start
    2023-02-09T02:34:39Z opencon thread start
    2023-02-09T02:34:39Z init message: Done loading
    2023-02-09T02:34:39Z msghand thread start