I live in western Europe, my country nor the other countries close to mine "crack cryptocurrency", "arrest people who use it" or "stop people to know about bitcoin". I think most of the American countries are in the same boat...

Sure, some western governements don't like crypto, they'd rather see it regulated or dissapear, but they defenately don't crack down, arrest or censor crypto mining or usage.

Sure, some other countries might actually do those things, but there are more than enough countries that leave crypto users alone, so i don't think the fact that cuba is also indifferent towards crypto doesn't have a major effect... This fact alone is most likely not the driving force behind bitcoin's upward trend

Your screenshot shows your domain... I realise by the fact that you wiped out your tld in some parts of the screenshot you want to keep this info private, so maybe you can remove the screenshot and replace it by a censored one

This being said, i did visit your domain, and it seems like your tld already has an x3 certificate... Is your btcpayserver located on a subdomain? In this case you have to make sure the correct block exists in your nginx site config and you have to execute:

certbot --nginx -d sub.domain.com

It's the subdomain you want a certificate for in case you installed btcpayserver on a subdomain (like i did).

Now, the error you see seems to be rather common... A quick google resulted in sollutions like this one: https://community.letsencrypt.org/t/solved-the-client-lacks-sufficient-authorization-404-not-found/50894
Apparently, in this case, the posted deleted the AAAA record for his domain to solve the problem, but the post also helps the poster with some initial troubleshooting, you can repeat the steps they told him to do some troubleshooting for yourself

This being said, certbot does not have any authorisation towards your zone editor, it cannot modify dns zones all by itself, i have no idear how those records were entered?
Are you 100% certain you didn't do this? Did you ask support from somebody who is authorised to edit zone record (your hosting company for example?)? Did you give credentials to a thirth party (a partner, a friend)?

From this follow-up question, i can deduct you might be missing some background information about how bitcoin actually works. I'm not trying to insult you or anything, crypto is quite complex to grasp at first, so it's perfectly fine to have some confusions when you first enter this community.

the TL;DR;, simplified answer: bitcoin is not stored in a wallet or on a device...

Your wallet holds private keys (or a master private key from which other private keys are derived). Next to this, your wallet might hold some meta-data (like labels, or some history that can be regenerated by re-parsing the blockchain). This meta-data is actually "unimportant" (at least from a technical point of view), it is not needed to spend your funds, and some of it can be recreated by parsing the blockchain...

Your wallet derives your public key(s) from these private key(s). Those public key(s) are hashed to form your address.

When somebody funds your address, he/she is basically just broadcasting a transaction to the network that uses unspent outputs from the UTXO db as an input, while creating one (or more) unspent outputs funding your address... These transactions are stored on the blockchain (the decentral ledger), NOT in your wallet... The only important thing your wallet stores is your master private key (in ledger's case... Ledger is a HD wallet witch uses a xprv, not random keys), or your randomly-generated private keys... When you restore your wallet with a seed phrase, the new wallet will contain exactly the same master private key as the original wallet, so it'll be able to sign transactions spending the same unspent outputs...

I've dug in my documentation... But tbh, this documentation was just for my personal use... I usually leave out all the steps i can figure out by myself, by reading the manual or by using the help functionality... So it is possible you'll have to test and read instead of just copy/pasting the following steps:

Basically, just follow the build instructions on: https://electrum.org/#download

Then run electrum  as a daemon:

create a wallet:

load the wallet:

set the port

get the authentication

then, start messing with curl untill you've got your request figured out, and then implement it in whatever language you want...

yup, you can use electrum..

You need to run electrum headless as a daemon... create a wallet, load your wallet

https://electrum.readthedocs.io/en/latest/merchant.html
https://electrum.readthedocs.io/en/latest/jsonrpc.html

IIRC, schildbach wallet was the first android wallet available... I have no idear what the minimum android version for the current release is tough... No harm in trying it out (i guess). AFAIK, it doesn't have any vulnerability's (but, truth be told, i haven't used this wallet in ages, so you should DYOR before testing)/

The minimum android version isn't shown on the google play store, and i don't have an android 4 device laying around, so i have no way of testing it out.

I would, however, urge you to be carefull when installing a bitcoin wallet on a device with such an old os... How long since android 4 received any security patches?

when initialising your device, you'll be presented with a seed phrase and you'll be asked to write this phrase down.

If you ever break/lose your wallet, you can buy a new one and restore it using said seed phrase... Or if you're in a hurry, you can use electrum to restore your wallet using exactly the same seed... However, when using electrum to restore from seed you should consider your wallet to be compromised... But it's nice to know this is possible in case there's a sense of urgency.

By the way, this is exactly why you should write the seed phrase on paper, and never store it online. Also, make sure you store the paper on a safe place... In order to protect you against somebody finding your seed, you can use a passphrase:
https://support.ledger.com/hc/en-us/articles/115005214529-Advanced-passphrase-security

It seems the first couple of outputs are actually some sort of spam, leading to https: [slash] [slash] memo [dot] sv [slash] topic [slash] hmwyda

Maybe the dust is meanth for the receivers to check the transaction funding their address and following the spam link?

Ok, you updated your OP since i last posted and gave some extra information that make things a bit clearer.

Where did you get these wallet files from? I followed the link in your signature, and it seems you're trying to sell a collection of "hacked" or "lost" encrypted wallets with big balances in them.
Is this one of these wallets? Some of them are known to be edited... Some of these wallets are edited in such a way the seller can provide nice screenshots to his victims clients and sell them worthless wallets for a big premium by manually changing the wallet files.

You've just shown 2 screenshots of the qt wallet, these screenshots look 100% fine...
It's impossible for us to check any explorer since the screenshot doesn't show addresses or tx id's, so we're unable to tell you if you found a bug or not...

However, it would supprise me if something was wrong... >95% chance either your wallet file was messed with, something went wrong during synchronisation or the explorer you used messed up (some explorers have quite a lot of bugs).

Am i missing something?

You're checking 2 different wallets and you see 2 different history's?

I do hope you're working together with law enforcement, especially for the users that prefer children... I mean, knowing the ip of pedophiles and not going to the police is morally wrong (imho).

I'm not a monero user myself, so i don't really know what this ciphertrace vulnerability is, but it'll certainly make a nice read once i have some spare time...

^^ exactly!

I'm sorry if this is for real, but you (the OP) might aswell be somebody who has a problem with Parodium, and decided to claim to be the original owner so DT would tag the account and cause harm to the real owner.

I'm not saying this is the case here (defenately not), but i've seen stranger things happen in the past... If you can provide a signed message with a staked address, i'll tag the account straight away... If not, i'd discourage others from tagging the account due to the fact they could be helping somebody with a personal vendetta instead of helping the victim of a hacked account.

It's the same point as everything else in your thread: a learning experience... The point of setting up a pool for such a cloned coin is exactly the same point as having a block explorer or an spv wallet... After all: you can easily parse those couple of blocks manually instead of using an explorer, and you don't need an SPV wallet if the total size of your blockchain is only a couple Mb...

98 - mocacinno

Thanks!

A long time ago, i have created my own (private) coins for learning purposes... So it's defenately possible.
I stared with litecoin's codebase since at that time it still had the code for a cpu miner, so that made things easyer to find the first couple of blocks. I had that network running between a couple of home computers for weeks...

I also setup a block explorer... Can't remember which one tough... And I cloned P2Pool and setup my own mining pool..

IIRC, the whole thing took me about a week... Including adapting litecoin's codebase for my own "coin", compiling linux and windows binaries, setting up an explorer and a pool... But since it was a private project I never applied any updates or improvements.

Later on, i got fed up by the sheer amount of low-effort worthless altcoins flooding the market, so i made a proof-of-concept to prove anybody with some basic skills could push an altcoin to the market in a couple of hours, so i created mocacoin in a timespan of 3 or 4 hours (IIRC): https://www.mocacinno.com/mocacoin
It's based on monero's coinbase (or was it based on a clone of a clone of XMR... Don't remember)

So, if that's TL;DR; : sure, it's possible to create your own altcoin, as long as it's for learning purposes... an explorer: sure... a pool: sure.... electrum: sure (i haven't done this personally, but i don't see why not)...

i think you do need a tld (domainname) if you want to use certbot... IIRC, you'd have to execute following command after nginx is running correctly:


There's always the option of creating a self signed certificate, but you'll probably be confronted with warning messages later on if you do so...

I'm not a spreadsheet updater per sé... But i did my fair share of scripting.

IF there's a source available for the data that's parseable (or even better, an api) i can probably write you a python script that fetches the data and places it in a spreadsheet automatically. That way you don't have to find somebody to manually update your spreadsheet, but you can just run the script yourself and have an automatically generated sheet available.

Offcourse, per hour, it's more expensive to let somebody write a script like this compared to finding somebody to update your values.. Only consider this if there's a nice (parseable, stable) source available and if you want frequent updates that require quite some time to complete.

It's pretty "simple"... First, check your transaction fee (in sat/vbyte). One of the easyest ways of doing this is looking up your tx on a block explorer:
https://blockstream.info/tx/4054df5d554a3a1c4a05f8582d31449db69f0b80c8dda4d507f8b41d2e070fcb

you payed 1 sat/vbyte

The, you look at the current state of the mempool on a site like this one:
https://jochen-hoenicke.de/queue/#0,24h

If you look at the bottom grahph, and you hover over the last couple of minutes, you'll see something like this:


A block can contain up to 1Mb of transaction data (not counting the witness data). You see that you should have payed a fee of >250 sat/vbyte to be in the top 1 Mb of the mempool.

You, on the other hand, are in the bottom 63 Mb... This means that IF everybody would suddenly stop broadcasting transactions, it would still take another >60 blocks before you'd have a decent chance of having your transaction confirmed...
~6 blocks/hours => >10 hours... and that is IF everybody would completely stop broadcasting transactions.

In your case it could take several days, even weeks or months before your transaction ends up in a block. There is no way of telling. Everybody who even attempts to give you a real estimation is basically guessing...

You didn't opt-in rbf, you payed less than 10 sat/vbyte, so if you want to speed up your transaction you'll have to pay a big mining pool (like viabtc) or execute a CPFP: https://bitcointalk.org/index.php?topic=5285192

You could always write a small script that fetches the price from https://api.coindesk.com/v1/bpi/currentprice.json, put it in your crontab then push the output to notify-send or kdialog or yfiton or conky or use ImageMagick to print the output to your background image or... whatever tool is available for your distro/desktop env