|
io alla fine non ho capito per chi non ha acquistato(ma ha minato eoni fa a costo zero praticamente) cosa deve fare? deve compilare il quadro RT anche se non genera plusvalenza oppure paga le tasse solo se supera i famosi 51k, sui depositi negli exchange?
nel RW quale sarebbe il valore iniziale, i bitcoin in possesso per il loro controvalore in euro al 1/1/2022? stessa cosa per il riquadro 8 da compilare
da quello che ho capito per gli atipici basta compilare l'RW e non sussiste la tassazione se non superi i 51k di giacenza(non viene considerato il wallet privato), quindi è solo ai fini del riciclaggio
esempio pratico con 1 btc su un wallet privato, dichiaro nel RW con i vari codici, e nel valore iniziale metto 1 x 40k circa (che era il valore di btc al 1/1/2022), stessa cosa con 1x 15k circa per il valore finale al 31/12/2022, è corretto?
|
|
|
|
I don't know, that's my best guess since Lucius seems to be rather dumbfounded by why they received the personal message in the first place.
which doesn't make sense, the reason is because is trying to hide that he was him in telegram poiting his profile, to trick me and telling to send him a msg to create this topic, it's so straightforward it's not even funny PM has been reported to admins/global mods asking them to confirm its authenticity.
The above post I made is obviously speculation, and I guess it depends on if any other evidence is brought forward. However, at the moment it seems like both users don't actually know what went on exactly.
Do you really think that I contacted someone on Telegram and asked to buy their bitcointalk account in such a stupid and naive way? It is clear to me what happened here, and I also have proof in the PM where I am very clearly and unequivocally offered to buy a bitcointalk account - and the person selling it claims that he communicated with me via Telegram without any concrete proof - is the proof public profile link which anyone can copy and place anywhere? sure for no reaosn and out of nowhere i contacted u to sell my account, the only rewson is because you were the one of telegram asking for that btw i'm not seeing that i didn't send that pm, i'm saying that he tell me to do so, to create this topic, that's my point the liar is him that keep saying he didn't contacted me via telegram and saying all the stuff in that screen |
|
|
|
sure some random guy pointed your profile in A PRIVATE chat on telegram, come on don't be a moron, that is an undeniable proof that you comunicate wiht me via telegram, otherwise i would never send a private msg to you
you are a lier nothing else, and your screen don't prove anything either, there are plenty of way to edit any screen or even video so...
Your reaction for his proof itself says who is talking the truth here. Anyway he posted the proof about the PM he received from your account so what is you answer or atleast say that he edited the picture and trying to portray you as an account seller.  Anyone ready for the drama? he is the one that contacted me via telegram if you think that is not him you must have some serious logic flaw as i said that is not a proof, you can edit any screen easily |
|
|
|
|
sure some random guy pointed your profile in A PRIVATE chat on telegram, come on don't be a moron, that is an undeniable proof that you comunicate wiht me via telegram, otherwise i would never send a private msg to you
you are a lier nothing else, and your screen don't prove anything either, there are plenty of way to edit any screen or even video so...
|
|
|
|
this guy tricked me just to be able to prove that im selling my account, he said he want to buy the account (which was a lie), i can prove that with screen if you believe a guy like this is trustworthy, draw your conclusions he also blatantly say that we didn't communicate via telegram which is a pure lie here  |
|
|
|
ok i fixed it by redownloading the whole chain, sometimes it happen, still don't know why It seems your Bitcoin core before was previously pruned and did you just disable it recently according to this log "Block files have previously been pruned".
Do you mind running bitcoin core with -reindex this can mostly solve syncing issues.
And I just want to know if you change or add something related to the network under bitcoin.conf file before it might be one of the reasons why it's not syncing.
yeah i use prune 200k cuz i have obly 500 gb of storage, but i didn't change that, when launching the new version i didn't know about reindex, i'll use that next time i have this issue |
|
|
|
here the debug 2023-02-22T12:02:49Z Bitcoin Core version v24.0.1 (release build)
2023-02-22T12:02:49Z Qt 5.15.5 (static), plugin=windows (static)
2023-02-22T12:02:49Z Static plugins:
2023-02-22T12:02:49Z QWindowsIntegrationPlugin, version 331520
2023-02-22T12:02:49Z QWindowsVistaStylePlugin, version 331520
2023-02-22T12:02:49Z Style: windowsvista / QWindowsVistaStyle
2023-02-22T12:02:49Z System: Windows 10 Version 2009, x86_64-little_endian-llp64
2023-02-22T12:02:49Z Screen: \\.\DISPLAY1 2560x1440, pixel ratio=1.0
2023-02-22T12:02:49Z Using the 'sse4(1way),sse41(4way),avx2(8way)' SHA256 implementation
2023-02-22T12:02:49Z Using RdRand as an additional entropy source
2023-02-22T12:02:49Z Default data directory C:\Users\Amph\AppData\Roaming\Bitcoin
2023-02-22T12:02:49Z Using data directory C:\Users\Amph\AppData\Roaming\Bitcoin
2023-02-22T12:02:49Z Config file: C:\Users\Amph\AppData\Roaming\Bitcoin\bitcoin.conf (not found, skipping)
2023-02-22T12:02:49Z Setting file arg: prune = "1907"
2023-02-22T12:02:49Z Setting file arg: wallet = [""]
2023-02-22T12:02:49Z Command-line arg: prune="220000"
2023-02-22T12:02:49Z Using at most 125 automatic connections (2048 file descriptors available)
2023-02-22T12:02:49Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely…"
2023-02-22T12:02:49Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2023-02-22T12:02:49Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2023-02-22T12:02:49Z Script verification uses 7 additional threads
2023-02-22T12:02:49Z scheduler thread start
2023-02-22T12:02:49Z Using wallet directory C:\Users\Amph\AppData\Roaming\Bitcoin\wallets
2023-02-22T12:02:49Z init message: Verifying wallet(s)…
2023-02-22T12:02:49Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2023-02-22T12:02:49Z Using wallet C:\Users\Amph\AppData\Roaming\Bitcoin\wallets\wallet.dat
2023-02-22T12:02:49Z BerkeleyEnvironment::Open: LogDir=C:\Users\Amph\AppData\Roaming\Bitcoin\wallets\database ErrorFile=C:\Users\Amph\AppData\Roaming\Bitcoin\wallets\db.log
2023-02-22T12:02:49Z Using /16 prefix for IP bucketing
2023-02-22T12:02:49Z init message: Loading P2P addresses…
2023-02-22T12:02:49Z Loaded 71410 addresses from peers.dat 265ms
2023-02-22T12:02:49Z init message: Loading banlist…
2023-02-22T12:02:49Z banlist.dat ignored because it can only be read by Bitcoin Core version 22.x. Remove "C:\Users\Amph\AppData\Roaming\Bitcoin\banlist.dat" to silence this warning.
2023-02-22T12:02:49Z SetNetworkActive: true
2023-02-22T12:02:49Z Cache configuration:
2023-02-22T12:02:49Z * Using 2.0 MiB for block index database
2023-02-22T12:02:49Z * Using 8.0 MiB for chain state database
2023-02-22T12:02:49Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2023-02-22T12:02:49Z init message: Loading block index…
2023-02-22T12:02:49Z Assuming ancestors of block 00000000000000000009c97098b5295f7e5f183ac811fb5d1534040adb93cabd have valid signatures.
2023-02-22T12:02:49Z Setting nMinimumChainWork=00000000000000000000000000000000000000003404ba0801921119f903495e
2023-02-22T12:02:49Z Prune configured to target 220000 MiB on disk for block and undo files.
2023-02-22T12:02:49Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
2023-02-22T12:02:49Z Opening LevelDB in C:\Users\Amph\AppData\Roaming\Bitcoin\blocks\index
2023-02-22T12:02:49Z Opened LevelDB successfully
2023-02-22T12:02:49Z Using obfuscation key for C:\Users\Amph\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2023-02-22T12:02:52Z LoadBlockIndexDB: last block file = 3416
2023-02-22T12:02:52Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=3626551, heights=776979...776979, time=2023-02-17...2023-02-17)
2023-02-22T12:02:52Z Checking all blk files are present...
2023-02-22T12:02:53Z LoadBlockIndexDB(): Block files have previously been pruned
2023-02-22T12:02:53Z Opening LevelDB in C:\Users\Amph\AppData\Roaming\Bitcoin\chainstate
2023-02-22T12:02:53Z Opened LevelDB successfully
2023-02-22T12:02:53Z Using obfuscation key for C:\Users\Amph\AppData\Roaming\Bitcoin\chainstate: 66b05a406ad5780b
2023-02-22T12:02:54Z Loaded best chain: hashBestChain=00000000000000000003267474564f9de9bfaf4cdb845b7714a4058444342c8c height=776978 date=2023-02-17T09:55:26Z progress=0.998407
2023-02-22T12:02:54Z init message: Verifying blocks…
2023-02-22T12:02:54Z Verifying last 6 blocks at level 3
2023-02-22T12:02:54Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2023-02-22T12:02:56Z No coin database inconsistencies in last 6 blocks (8309 transactions)
2023-02-22T12:02:56Z block index 6212ms
2023-02-22T12:02:56Z init message: Loading wallet…
2023-02-22T12:02:56Z BerkeleyEnvironment::Open: LogDir=C:\Users\Amph\AppData\Roaming\Bitcoin\wallets\database ErrorFile=C:\Users\Amph\AppData\Roaming\Bitcoin\wallets\db.log
2023-02-22T12:02:56Z [default wallet] Wallet file version = 10500, last client version = 240001
2023-02-22T12:02:56Z [default wallet] Keys: 2383 plaintext, 0 encrypted, 2383 w/ metadata, 2383 total. Unknown wallet records: 0
2023-02-22T12:02:56Z [default wallet] Wallet completed loading in 46ms
2023-02-22T12:02:56Z [default wallet] setKeyPool.size() = 2000
2023-02-22T12:02:56Z [default wallet] mapWallet.size() = 212
2023-02-22T12:02:56Z [default wallet] m_address_book.size() = 64
2023-02-22T12:02:56Z init message: Pruning blockstore…
2023-02-22T12:02:56Z block tree size = 776987
2023-02-22T12:02:56Z nBestHeight = 776978
2023-02-22T12:02:56Z loadblk thread start
2023-02-22T12:02:56Z torcontrol thread start
2023-02-22T12:02:56Z Bound to 127.0.0.1:8334
2023-02-22T12:02:56Z Bound to [::]:8333
2023-02-22T12:02:56Z Bound to 0.0.0.0:8333
2023-02-22T12:02:56Z Loaded 2 addresses from "anchors.dat"
2023-02-22T12:02:56Z 2 block-relay-only anchors will be tried for connections.
2023-02-22T12:02:56Z init message: Starting network threads…
2023-02-22T12:02:56Z net thread start
2023-02-22T12:02:56Z dnsseed thread start
2023-02-22T12:02:56Z addcon thread start
2023-02-22T12:02:56Z opencon thread start
2023-02-22T12:02:56Z init message: Done loading
2023-02-22T12:02:56Z Waiting 300 seconds before querying DNS seeds.
2023-02-22T12:02:56Z msghand thread start
2023-02-22T12:02:56Z GUI: Platform customization: "windows"
2023-02-22T12:02:56Z New outbound peer connected: version: 70016, blocks=777788, peer=0 (block-relay-only)
2023-02-22T12:02:57Z New outbound peer connected: version: 70016, blocks=777788, peer=1 (block-relay-only)
2023-02-22T12:02:59Z Imported mempool transactions from disk: 3941 succeeded, 0 failed, 58 expired, 0 already there, 0 waiting for initial broadcast
2023-02-22T12:02:59Z loadblk thread exit
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS Shell Dlg 2", script 12
2023-02-22T12:03:09Z GUI: OpenType support missing for "Arial", script 12
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS UI Gothic", script 12
2023-02-22T12:03:09Z GUI: OpenType support missing for "SimSun", script 12
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS Shell Dlg 2", script 14
2023-02-22T12:03:09Z GUI: OpenType support missing for "Arial", script 14
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS UI Gothic", script 14
2023-02-22T12:03:09Z GUI: OpenType support missing for "SimSun", script 14
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS Shell Dlg 2", script 32
2023-02-22T12:03:09Z GUI: OpenType support missing for "Arial", script 32
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS UI Gothic", script 32
2023-02-22T12:03:09Z GUI: OpenType support missing for "SimSun", script 32
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS Shell Dlg 2", script 19
2023-02-22T12:03:09Z GUI: OpenType support missing for "Arial", script 19
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS UI Gothic", script 19
2023-02-22T12:03:09Z GUI: OpenType support missing for "SimSun", script 19
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS Shell Dlg 2", script 11
2023-02-22T12:03:09Z GUI: OpenType support missing for "Arial", script 11
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS UI Gothic", script 11
2023-02-22T12:03:09Z GUI: OpenType support missing for "SimSun", script 11
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS Shell Dlg 2", script 13
2023-02-22T12:03:09Z GUI: OpenType support missing for "Arial", script 13
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS UI Gothic", script 13
2023-02-22T12:03:09Z GUI: OpenType support missing for "SimSun", script 13
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS Shell Dlg 2", script 20
2023-02-22T12:03:09Z GUI: OpenType support missing for "Arial", script 20
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS UI Gothic", script 20
2023-02-22T12:03:09Z GUI: OpenType support missing for "SimSun", script 20
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS Shell Dlg 2", script 16
2023-02-22T12:03:09Z GUI: OpenType support missing for "Arial", script 16
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS UI Gothic", script 16
2023-02-22T12:03:09Z GUI: OpenType support missing for "SimSun", script 16
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS Shell Dlg 2", script 17
2023-02-22T12:03:09Z GUI: OpenType support missing for "Arial", script 17
2023-02-22T12:03:09Z GUI: OpenType support missing for "MS UI Gothic", script 17
2023-02-22T12:03:09Z GUI: OpenType support missing for "SimSun", script 17
2023-02-22T12:03:53Z New outbound peer connected: version: 70015, blocks=777789, peer=2 (outbound-full-relay)
2023-02-22T12:04:00Z New outbound peer connected: version: 70016, blocks=777789, peer=3 (outbound-full-relay)
2023-02-22T12:04:14Z New outbound peer connected: version: 70015, blocks=777789, peer=4 (outbound-full-relay)
2023-02-22T12:04:35Z New outbound peer connected: version: 70016, blocks=777789, peer=6 (outbound-full-relay)
2023-02-22T12:04:36Z New outbound peer connected: version: 70016, blocks=777789, peer=7 (outbound-full-relay)
2023-02-22T12:04:37Z New outbound peer connected: version: 70016, blocks=777789, peer=8 (outbound-full-relay)
2023-02-22T12:05:30Z New outbound peer connected: version: 70016, blocks=777789, peer=9 (outbound-full-relay)
2023-02-22T12:05:31Z New outbound peer connected: version: 70015, blocks=777789, peer=10 (outbound-full-relay)
2023-02-22T12:05:53Z New outbound peer connected: version: 70016, blocks=777789, peer=11 (outbound-full-relay)
2023-02-22T12:05:55Z New outbound peer connected: version: 70016, blocks=777789, peer=12 (outbound-full-relay)
2023-02-22T12:06:24Z New outbound peer connected: version: 70016, blocks=777789, peer=13 (outbound-full-relay)
2023-02-22T12:06:44Z New outbound peer connected: version: 70016, blocks=777789, peer=14 (outbound-full-relay)
2023-02-22T12:06:46Z New outbound peer connected: version: 70015, blocks=777788, peer=16 (outbound-full-relay)
2023-02-22T12:06:46Z New outbound peer connected: version: 70015, blocks=777789, peer=17 (outbound-full-relay)
2023-02-22T12:06:59Z New outbound peer connected: version: 70015, blocks=777789, peer=18 (outbound-full-relay)
2023-02-22T12:07:00Z New outbound peer connected: version: 70016, blocks=777789, peer=19 (outbound-full-relay)
2023-02-22T12:07:11Z New outbound peer connected: version: 70016, blocks=777789, peer=20 (outbound-full-relay)
2023-02-22T12:07:36Z New outbound peer connected: version: 70016, blocks=777790, peer=21 (outbound-full-relay)
|
|
|
|
|
anyone is experiencing the same thing? there was a consensus warning initially when i swiched, now it's not there anymrore, and it's not synching either
|
|
|
|
i can't sinc anymore with the last version, anyone have the some problem?
No, i can sync whether on mainnet, testnet or signet. You might want to ask help on "Bitcoin Technical Support" board while providing some information (e.g. debug log, how do you connect to internet). i didn't change anything about internet connection or firewall therefore it's not that, there was a warning about consensus when i switched from 23 to 24 version, then the warning disappeared and now it's not synching anymore |
|
|
|
|
i can't sinc anymore with the last version, anyone have the some problem?
|
|
|
|
|
i would like to apply if any spot left
Username: Amph
BTC SegWit Address: bc1qdja7hkfqtwcvzdek5e4838wrczy7d67rsrsyzu
|
|
|
|
Bitcointalk Username: Amph Profile Link: https://bitcointalk.org/index.php?action=profilePost Count: 29021 Forum Rank: Legendary member Are you able to wear our Signature, Avatar & Personal Text? yes Stake Username: Amph can't access stake.com now to have the username there |
|
|
|
|
it was kava back then but now everything is falling, i'm sticking with cosmos coin, they look promising, so kava is still okish right now
|
|
|
|
|
i would like to join, i know i have no merit in the last 120 days, but i can work on that
Current number of post (Including this one): 29019
Rank: Legendary
bech32 address: bc1qdja7hkfqtwcvzdek5e4838wrczy7d67rsrsyzu
Merit earned in the last 120 days: none
|
|
|
|
Da quanto ho capito per le crypto possedute prima del 2018 non vi è l'obbligo di dichiarare, quindi tutto risolto 😆
anche qua, come lo si può dimostrare? soprattutto se è roba ottenuta da mining o da scambi crypto/crypto fatti secoli fa? Parlando di bitcoin, ci sono degli indirizzi. Puoi dimostrare che tutti gli indirizzi che sono stati usati dal 2018 in poi erano sotto il tuo controllo (puoi farlo, vero?) Nessuno può dimostrare niente a nessuno, nessun wallet è associato a un codice fiscale, per come la vedo io posso presentare ad un ipotetico controllo un wallet dove ci sono dentro poco più di 10€ di Bitcoin è dire io posseggo solo questi , e invece ne ho altri con migliaia di €. Come faranno a dimostrare che sto dicendo il falso? Bravo... è una specie di postulato che è sempre stato detto qui dentro: Non è dimostrabile che una persona abbia N indirizzi se non per autocertificazione Non è dimostrabile che SOLO quella persona sia titolare di una private key Non è dimostrabile che "ah, mi son dimenticato il seed" "ah, me lo sono ricordato" Bitcoin on chain non è regolamentabile Unica cosa a cui ci si può aggrappare con logica è il cashout in fiat. Puoi sicuramente dimostrare che i bitcoin in tuo possesso e quindi le chiavi private da te possedute lo sono da una certa data basta usare la blockchain, il fatto che in passato quei bitcoin potevano essere di qualcun altro che rilevanza ha... Se ti accusano non so, di averlo rubato nel 2018 o cose del genere, devono avere le prove e ovviamente non ce l'hanno A parte che posso dimostrare che i vari wallet che detenevano i bitcoin da prima del 2018, sono stati creati con il computer che ho acquistato, cosa anch'essa dimostrabile con fattura su amazon per dire, quindi questo dimostrerebbe in teoria che sono esclusivamente miei |
|
|
|
|
Da quanto ho capito per le crypto possedute prima del 2018 non vi è l'obbligo di dichiarare, quindi tutto risolto 😆
|
|
|
|
|
Ovviamente non perdono mai l'occasione per screditare random, quando capita il momento giusto, guarda caso questi articoli non escono duranti i pump stellari
|
|
|
|
Ma per i bitcoin non dichiarati fino a che anno nel passato? Non penso anche roba del 2010, si riferiscono massimo a quelli del 2018, per quelli prima niente immagino o mi sbaglio?
Ma nel 2018 cosa è successo poi? Hanno minato il Genesis Block dello stato italiano? penso xchè ci fu il primo picco a 20k o gu di li, negli anni precedenti valeva 200 euro quindi nessuno se lo cagava Il mio non vuole essere un incoraggiamento a non pagare le tasse, ma come si commenta il buttare via cartelle sotto i 1000€ perché non convenienti da recuperare, unito a norme sulla tassazione di difficile applicazione... Ma più che altro non sono chiari, non pago tasse di cose sulle quali non vige nessuna chiarezza |
|
|
|
Ma per i bitcoin non dichiarati fino a che anno nel passato? Non penso anche roba del 2010, si riferiscono massimo a quelli del 2018, per quelli prima niente immagino o mi sbaglio?
Ma nel 2018 cosa è successo poi? Hanno minato il Genesis Block dello stato italiano? penso xchè ci fu il primo picco a 20k o gu di li, negli anni precedenti valeva 200 euro quindi nessuno se lo cagava |
|
|
|
|
Ma per i bitcoin non dichiarati fino a che anno nel passato? Non penso anche roba del 2010, si riferiscono massimo a quelli del 2018, per quelli prima niente immagino o mi sbaglio?
|
|
|
|
|
Show Posts
