Any alternative to dumpwallet and importwallet on taproot wallets on bitcoin core for backup purposes? https://developer.bitcoin.org/reference/rpc/importwallet.html
Читать полностью…Hi guys, maybe someone can help me here: is there a way to extract from Bitcoin Core some stats about the totale number of wallets? like an historical series of how the number of wallets with greater than zero balance evolved over time? or just a snapshots of all the wallet balance at a given period of time... than I could derive my stats.
Читать полностью…I’m looking for C++ software engineers familiar with the Blockstream Elements codebase and with Bitcoin Sidechains in general. Who’s interested please DM me
Читать полностью…Does anyone know a way how one can recover tether funds if one has send to a wrong dust address ?
Читать полностью…are they really new found members of the community if they're buying ETF shares? lol
Читать полностью…BlackRock ETF Drawbacks - risk of eventual fractional reserve Bitcoin holdings - BlackRock pushes ESG & other woke / socialist stupidity - they are active investors who are used to control - increases odds of a fork or code war or attempt to influence Benefits - massive AUM of $10T, 5% of BlackRock’s AUM = the market cap of all Bitcoin - institutional influence & distribution - opens door for other competitors
Читать полностью…Yes everyone can join, but in the ishares trust spot etf there is a part that says they decide where they will stay in an event of a fork and which network they ll follow
Читать полностью…Hi everyone, I am compiling my Bitcoin Core myself but I cannot compile version v25.0
version v24.1
compiles fine but with version 25 I am getting this error:
In file included from ipc/capnp/protocol.cpp:8:
./ipc/capnp/init.capnp.proxy.h:25:52: error: expected type-specifier before ‘AUTO_RETURN’
25 | template<typename S> static auto get(S&& s) -> AUTO_RETURN(s.getThreadMap())
| ^~~~~~~~~~~
./ipc/capnp/init.capnp.proxy.h:25:52: error: expected initializer before ‘AUTO_RETURN’
./ipc/capnp/init.capnp.proxy.h:28:78: error: expected type-specifier before ‘AUTO_RETURN’
28 | template<typename S, typename... A> static auto init(S&& s, A&&... a) -> AUTO_RETURN(s.initThreadMap(std::forward<A>(a)...))
| ^~~~~~~~~~~
./ipc/capnp/init.capnp.proxy.h:28:78: error: expected initializer before ‘AUTO_RETURN’
./ipc/capnp/init.capnp.proxy.h:36:52: error: expected type-specifier before ‘AUTO_RETURN’
36 | template<typename S> static auto get(S&& s) -> AUTO_RETURN(s.getContext())
| ^~~~~~~~~~~
./ipc/capnp/init.capnp.proxy.h:36:52: error: expected initializer before ‘AUTO_RETURN’
./ipc/capnp/init.capnp.proxy.h:39:78: error: expected type-specifier before ‘AUTO_RETURN’
39 | template<typename S, typename... A> static auto init(S&& s, A&&... a) -> AUTO_RETURN(s.initContext(std::forward<A>(a)...))
| ^~~~~~~~~~~
./ipc/capnp/init.capnp.proxy.h:39:78: error: expected initializer before ‘AUTO_RETURN’
./ipc/capnp/init.capnp.proxy.h:47:52: error: expected type-specifier before ‘AUTO_RETURN’
47 | template<typename S> static auto get(S&& s) -> AUTO_RETURN(s.getResult())
| ^~~~~~~~~~~
./ipc/capnp/init.capnp.proxy.h:47:52: error: expected initializer before ‘AUTO_RETURN’
./ipc/capnp/init.capnp.proxy.h:50:78: error: expected type-specifier before ‘AUTO_RETURN’
50 | template<typename S, typename... A> static auto init(S&& s, A&&... a) -> AUTO_RETURN(s.initResult(std::forward<A>(a)...))
| ^~~~~~~~~~~
./ipc/capnp/init.capnp.proxy.h:50:78: error: expected initializer before ‘AUTO_RETURN
./autogen.shЧитать полностью…
make -C depends NO_QT=1 NO_WALLET=1 MULTIPROCESS=1 -j 8
export CONFIG_SITE=/data/bitcoin/depends/x86_64-pc-linux-gnu/share/config.site
./configure CXXFLAGS="$CXXFLAGS" --disable-wallet --disable-bench --without-gui --without-miniupnpc --without-natpmp --enable-multiprocess
make -j 8
sudo make install
I think that's going to be quite computationally expensive. you'd have to replay the chain and do a triple nested for loop... for block, for tx, for vout do you really need the information to be accurate? if not I'd suggest riding on someone else's coat tails. Suggest find an existing chart online from a provider like blocksights or such and use some online chart to table software if the data is not available raw via api.
Читать полностью…From exchange to a private wallet? But instead to the real address sended to the dust address sort of like being target to a clipboard attack or something of that nature.
Читать полностью…and we (hopefully) don't run around sounding alarms about exchanges every day, just general reluctance and education towards people with enough bitcoin to avoid them
Читать полностью…to me thats overextending; not your keys not your bitcoin is long known, we should protecting people with the keys
Читать полностью…Yes they are new and they are dinosour investors like charlie and warren who are scared and dont understand new things go thru their friends on wall street to make more fiat profit they dont give a shit about btc
Читать полностью…Its not my problem, but it can be a problem to a newly found members of the community that can easily be misinformed or manipulated by rogue agents
Читать полностью…and thats fair, thats how governance is eventually done, by people selling one side and buying another
Читать полностью…So just like roger and jihan they may try to hyperinflate with btc paper so they can scam ppl
Читать полностью…@oriolpont
Please help and delte this
Is this @ adam3us actually the real adam back ?