An escrow is a trusted third partyYou are the buyer AND the escrow in this case, that's not how an escrow is supposed to work. What if your seller (the translator) completes his/her job and you (the buyer) refuse to pay? Wil you (the escrow) be able to impartially judge and still pay the seller while you (the buyer) refused to do so? Quickseller got shunned, red trusted, insulted,... because he was caught self-escrowing in the past. Don't repeat his mistake. |
|
|
|
Yes, it's green.
I just re-read your initial post, you said you got an error message (i originally missed this when i read your post)... Do you remember what it said? Maybe it wasn't a connection issue, maybe it had something to do with the fee, dust outputs, unconfirmed inputs,... |
|
|
|
You just 'saved' it and wasn't broadcast yet to the network.
You can safely delete it from the history by doing right-click->delete (do not right click to the label) and your previous balance should return.
This is correct. However, there might be an underlying problem with your connection that caused this issue... So you can safely remove the old transaction, but if you create a new transaction you might run into the same problem if you don't fix your connection... Is the button on the bottom right of the electrum window green? |
|
|
|
1 - mocacinno Thanks  |
|
|
|
That was going to be in my next question.
But, that reinforces the belief that the nodes in the Lightning Network will evolve to become more specialized, and routing fees becoming higher than they are now. It also takes a valuable commodity, Bitcoins, staked in channels.
My main idear wasn't to make a profit, but rather learn the "new" (at that time) lightning protocol... I do hope that sooner or later, the fees might increase a little bit, but as for now: nobody knows I'm a bit curious,
1. What is average RAM usage after install all of these tools?
2. Does Bitcoin Core use most of the RAM in your case (since you use value 2048 for you dbcahce) ?
Yup, dbcache was set to 2048 to speed up the intial sync, afterwards it's perfectly fine to remove this parameter. Here you go (i've snipped all processes that had nothing to do with this particular stack) ps -o pid,user,%mem,command ax | sort -b -k3 -r
PID USER %MEM COMMAND
13827 bitcoin 18.3 /usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf
22686 bitcoin 0.7 /usr/bin/node /home/bitcoin/RTL/rtl.js
20476 bitcoin 0.6 /usr/local/bin/lightningd --daemon --conf /home/bitcoin/.lightning/bitcoin/lightningd.conf
21778 bitcoin 0.6 /usr/bin/node /home/bitcoin/c-lightning-REST/cl-rest.js
20487 bitcoin 0.0 /usr/local/libexec/c-lightning/lightning_hsmd
20489 bitcoin 0.0 /usr/local/libexec/c-lightning/lightning_gossipd
20488 bitcoin 0.0 /usr/local/libexec/c-lightning/lightning_connectd
20478 bitcoin 0.0 /usr/local/bin/../libexec/c-lightning/plugins/pay
20477 bitcoin 0.0 /usr/local/bin/../libexec/c-lightning/plugins/fundchannel
20479 bitcoin 0.0 /usr/local/bin/../libexec/c-lightning/plugins/autoclean
29533 nginx 0.0 nginx: worker process
29532 nginx 0.0 nginx: worker process
29531 nginx 0.0 nginx: worker process
cat /proc/meminfo
MemTotal: 2913960 kB
MemFree: 79220 kB
MemAvailable: 1919348 kB
Buffers: 3020 kB
Cached: 2067608 kB
SwapCached: 11496 kB
Active: 1341376 kB
Inactive: 1354236 kB
Active(anon): 362948 kB
Inactive(anon): 375720 kB
Active(file): 978428 kB
Inactive(file): 978516 kB
Unevictable: 4 kB
Mlocked: 4 kB
SwapTotal: 1048568 kB
SwapFree: 741632 kB
Dirty: 64 kB
Writeback: 0 kB
AnonPages: 615284 kB
Mapped: 105608 kB
Shmem: 113628 kB
Slab: 59592 kB
SReclaimable: 36760 kB
SUnreclaim: 22832 kB
KernelStack: 5104 kB
PageTables: 21064 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 2505548 kB
Committed_AS: 2735808 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 13956 kB
VmallocChunk: 34359720444 kB
HardwareCorrupted: 0 kB
AnonHugePages: 20480 kB
CmaTotal: 0 kB
CmaFree: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 182144 kB
DirectMap2M: 1914880 kB
DirectMap1G: 1048576 kB
top - 07:27:07 up 4 days, 4:39, 1 user, load average: 0.00, 0.03, 0.05
Tasks: 140 total, 1 running, 139 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 2.1 sy, 0.0 ni, 97.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 2913960 total, 85292 free, 727596 used, 2101072 buff/cache
KiB Swap: 1048568 total, 741632 free, 306936 used. 1919012 avail Mem
|
|
|
|
How much would your average monthly cost be for electricity, internet connection, maintenance, if you keep your Lightning node running for 24/7 that specializes in providing liquidity?
To be honest, i hire a dedicated server which i've partitioned into smaller VPS's. A dedicated box costs me €40/month, but i would be able to install 5 or 6 full stacks on such a dedicated server, so if you pool your resources with 3 other forum members, you'd have a nice VPS with plenty of resources for €10/month if you'd want to. If you want to do a home setup, much depends on the power draw of your machine... An avarage laptop draws 60 Watts (according to google), beause there's a lot of IO and system load, i'd guess a laptop running such a stack would draw a little bit more. 80 Watt * 24 hours * 31 days =~ 60 Kwh. In my country i pay about 30 cents per Kwh, so the cost of running a node on a home laptop would be ~€18/month, not including the wear and tear of the hardware. As you can see in the screenshot, i'll never break even (my node has been online for about 1 year and 3 months, and i've earned 1.2 satoshi's in routing fees) |
|
|
|
|
None that i can think off... The company i work for regularly hires senior consultants for other teams, i know senior consultants that charge >€1500/day, but they are specialized in niche consultancy (for example, setting up and configuring very specialised custom SAP sollutions), they have gained a lot of trust by working their way from junior to senior consultant, and they have to give way more than 50% of their income to the tax collector afterwards.
I think your main problem is that there are plenty of wordpress/graphic designer/motion designer/python experts from low wage countries... I don't think you'll be able to charge >$500/day (after taxes) by staying within your speciality (at least, not shortterm...).
I know you said: no lending... But getting a loan from a bank might be your only shot at getting $1500 in 3 days... Unless you're willing to do risky or degrading jobs.
|
|
|
|
|
I'm thinking about adding a walktrough on how to install btcpayserver on top of the above stack... But i haven't written any documentation about this process (yet)... So i'll either update this post in the future, or i'll remove it (if i decide adding btcpayserver is to much work)
|
|
|
|
RTLprereqs: running and synced bitcoin core, running lightningd (c-lightning)step 1: make sure you're user bitcoin, make sure you're in the home folder, install the prereqs whoami
pwd
cd ~
sudo yum install -y gcc-c++ make
sudo curl -sL https://rpm.nodesource.com/setup_12.x | sudo -E bash -
sudo yum install nodejs
step 2: clone and build c-lightning-REST (this is a prereq for RTL) git clone https://github.com/saubyk/c-lightning-REST
cd c-lightning-REST
npm install
cp sample-cl-rest-config.json cl-rest-config.json
sudo lsof -i :3001
sudo lsof -i :4001
if the lsof command return nothing, the cl-rest-config.json should not be edited, if an other service is listening to port 3001 or 4001, you'll need to edit cl-rest-config.json step 3: create a service file for c-lightning-REST sudo nano /etc/systemd/system/c-lightning-REST.service
step 4: fill c-lightning-REST.service [Unit]
Description=c-lightning-REST daemon
Wants=lightningd.service
After=lightningd.service
[Service]
ExecStart=/usr/bin/node /home/bitcoin/c-lightning-REST/cl-rest.js
User=bitcoin
Group=bitcoin
Restart=always
TimeoutSec=120
RestartSec=30
[Install]
WantedBy=multi-user.target
step 5: enable and start the service sudo systemctl enable c-lightning-REST.service
sudo service c-lightning-REST start
step 6: make sure you're back into your home folder step 7: clone and build RTL git clone https://github.com/Ride-The-Lightning/RTL.git
cd RTL
npm install
cp sample-RTL-Multi-Node-Conf.json RTL-Multi-Node-Conf.json
step 8: edit RTL-Multi-Node-Conf.json {
"multiPass": "very_strong_password",
"port": "3000",
"defaultNodeIndex": 1,
"SSO": {
"rtlSSO": 0,
"rtlCookiePath": "",
"logoutRedirectLink": ""
},
"nodes": [
{
"index": 1,
"lnNode": "C Lighting",
"lnImplementation": "CLT",
"Authentication": {
"macaroonPath": "/home/bitcoin/c-lightning-REST/certs/"
},
"Settings": {
"userPersona": "MERCHANT",
"themeMode": "NIGHT",
"themeColor": "TEAL",
"channelBackupPath": "/home/bitcoin/RTL/",
"bitcoindConfigPath": "/home/bitcoin/.bitcoin/",
"enableLogging": true,
"fiatConversion": false,
"lnServerUrl": "https://127.0.0.1:3001/v1"
}
}
]
step 9: create service file sudo nano /etc/systemd/system/RTL.service
step 10: fill RTL.service [Unit]
Description=RTL daemon
Wants=c-lightning-REST.service
After=c-lightning-REST.service
[Service]
ExecStart=/usr/bin/node /home/bitcoin/RTL/rtl.js
User=bitcoin
Group=bitcoin
Restart=always
TimeoutSec=120
RestartSec=30
[Install]
WantedBy=multi-user.target
step 11: enable and start RTL service sudo systemctl enable RTL.service
sudo service RTL start
HOWEVER, if you've installed RTL on a server without a desktop environment and/or without proper x server forewarding, you'll need to execute the following steps in order to be able to surf to RTL (the RTL daemon only listens on localhost port 3000, so i't not accessible on an external portstep 1: register a tld. If you don't want to spend any money, a .tk domain is free. Make sure there's an a-record for this domain that points to your server. If you really don't have a domain, contact me and i'll give you a free [yourname].mocacinno.com subdomain step 2: request a certificate for this domain using certbot sudo yum install nginx certbot
sudo certbot certonly
step 3: open nginx.conf nano /etc/nginx/nginx.conf
step 4: edit nginx.conf user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;
# Load dynamic modules. See /usr/share/doc/nginx/README.dynamic.
include /usr/share/nginx/modules/*.conf;
events {
worker_connections 1024;
}
stream {
upstream RTL {
server 127.0.0.1:3000;
}
server {
listen 3002 ssl;
proxy_pass RTL;
ssl_certificate /etc/letsencrypt/live/yourdomain.tld/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/yourdomain.tld/privkey.pem;
ssl_session_cache shared:SSL:1m;
ssl_session_timeout 4h;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
}
}
step 5: restart nginx sudo service nginx restart
step 6: you now have RTL up and running: https://yourdomain.tld:3002    
|
|
|
|
c-lightningprereqs: running and synced bitcoin corestep 1: make sure you're user bitcoin, make sure you're in the home folder, install the prereqs whoami
pwd
cd ~
sudo yum install -y autoconf automake boost-devel gcc-c++ git libdb4-cxx libdb4-cxx-devel libevent-devel libtool openssl-devel wget libsodium-devel gmp-devel sqlite-devel python34 asciidoc clang python2-devel pythong34-devel python34-pip
sudo pip3 install Mako
step 2: clone and build c-lightning git clone https://github.com/ElementsProject/lightning.git
cd lightning
git checkout v0.8.0
./configure
make -j $(nproc)
sudo make install
make sure you checkout the latest release (at the time of writing, this is v0.8.0, but later on this number will increase) step 3: create the service sudo nano /usr/lib/systemd/system/lightningd.service
step 4: fill lightningd.service [Unit]
Description=C-Lightning daemon
Requires=bitcoind.service
After=bitcoind.service
Wants=network-online.target
After=network-online.target
[Service]
ExecStart=/usr/local/bin/lightningd --daemon --conf /home/bitcoin/.lightning/bitcoin/lightningd.conf
User=bitcoin
Group=bitcoin
Type=forking
Restart=on-failure
# Hardening measures
####################
# Provide a private /tmp and /var/tmp.
PrivateTmp=true
# Mount /usr, /boot/ and /etc read-only for the process.
ProtectSystem=full
# Disallow the process and all of its children to gain
# new privileges through execve().
NoNewPrivileges=true
# Use a new /dev namespace only populated with API pseudo devices
# such as /dev/null, /dev/zero and /dev/random.
PrivateDevices=true
# Deny the creation of writable and executable memory mappings.
MemoryDenyWriteExecute=true
[Install]
WantedBy=multi-user.target
step 5: create conf file nano /home/bitcoin/.lightning/bitcoin/lightningd.conf
step 6: fill conf file network=bitcoin
log-level=debug
log-file=/home/bitcoin/.lightning/debug.log
daemon
alias=alias_for_your_node
step 7: enable and start the service sudo systemctl enable lightningd.service
sudo service lightningd start
step 8: monitor the startup progress tail -f /home/bitcoin/.lightning/debug.log
press "Ctrl-c" to stop the tail, after a while you might decide to decrease the log level (step 6) Finished... 
|
|
|
|
Bitcoin coreprereqs: running (base) systemstep 1: create service user, install prereqs adduser bitcoin
passwd bitcoin
usermod -aG wheel bitcoin
yum -y install epel-release
yum install -y autoconf automake boost-devel gcc-c++ git libdb4-cxx libdb4-cxx-devel libevent-devel libtool openssl-devel wget nano python3
su - bitcoin
step 2: verify you should see you're "bitcoin" and your current working directory is "/home/bitcoin" step 3: build git clone https://github.com/bitcoin/bitcoin.git
cd bitcoin
git checkout v0.19.0.1
./autogen.sh
./configure
make -j $(nproc)
sudo make install
make sure you checkout the latest release (at the time of writing, this is v0.19.0.1, but later on this number will increase) step 4: create password hash cd share/rpcauth/
python3 rpcauth.py the_username_of_the_user_you_want cleartext_password_unique_long
Caveat: the plaintext password will be saved in your history!! pick a unique one and/or clean up your history afterwards!!! step 5: make dir, create conf mkdir ~/.bitcoin
nano ~/.bitcoin/bitcoin.conf
step 6: fill bitcoin.conf daemon=1
server=1
maxmempool=50
mempoolexpiry=2
rpcauth=user_chose_in_step_4:hash_created_in_step_4
dbcache=2048
banscore=10
datadir=/home/bitcoin/.bitcoin/
step 7: create service file sudo nano /usr/lib/systemd/system/bitcoind.service
step 8: file bitcoind.service [Unit]
Description=Bitcoin daemon
After=network.target
[Service]
ExecStart=/usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf
# Make sure the config directory is readable by the service user
PermissionsStartOnly=true
# Process management
####################
Type=forking
Restart=on-failure
# Directory creation and permissions
####################################
# Run as bitcoin:bitcoin
User=bitcoin
Group=bitcoin
# Hardening measures
####################
# Provide a private /tmp and /var/tmp.
PrivateTmp=true
# Mount /usr, /boot/ and /etc read-only for the process.
ProtectSystem=full
# Disallow the process and all of its children to gain
# new privileges through execve().
NoNewPrivileges=true
# Use a new /dev namespace only populated with API pseudo devices
# such as /dev/null, /dev/zero and /dev/random.
PrivateDevices=true
# Deny the creation of writable and executable memory mappings.
MemoryDenyWriteExecute=true
[Install]
WantedBy=multi-user.target
step 9: enable and start bitcoind service sudo systemctl enable bitcoind.service
sudo service bitcoind start
step 10: final step: check if your node is syncing tail -f ~/.bitcoin/debug.log
once everything seems to be working, press "Ctrl-C" step 11: (optional), re-visit step 6 and remove the banscore variable and decrease dbcache Finished... Now you'll have to wait several hours for your node to sync... You can only proceed to the next step once this process is finished 
|
|
|
|
bitcoind, c-lightning and RTL on centos 7 (walktrough)I decided to write down some documentation on how to rebuild some of my services in case i ever faced a system crash, and because i more or less had all documentation on my system, i decided to update everything and publish it on this forum AND my blog... This way everybody could use my documentation to setup their own services of they ever wanted to. some remaks: - I'm not taking any political stance here... The lightning network has pro's and con's, it's not completely mature (yet). This thread is NOT for discussing LN merits or shortcomings, but merely a technical walk-trough on how to get things up and running
- my system specs: Centos 7, KVM VPS, 3 Gb RAM, 3vCPU's... The most important spec, however, is the disksize... A full node requires 278G at this moment, and there is a (theoritical) growth potential of ~17 Gb/month. Add some space for binaries, updates, builds, logs,... So you'll need at very least 350 Gb of free space on your filesystem
- not all VPS providers will deliver a VPS that has the same configuration... It's possible some prereqs were already met in my basic image, while you have to install them yourself (or vice-versa)
- i didn't document the firewall rules, because there are several possible firewall-implementations, and basically, if i'd have to go into the details of setting up firewallrules, i'd need a completely seperate firewall tutorial alltogether. If you have a clean (unused) VPS or you're installing a server in your HOME network (behind your own firewall), you *might* want to disable the firewall for testing puposes (re-enable it afterwards tough!!!)
- i didn't document the backup procedures. Always make sure you backup wallets, seeds,...
- no guarantee... If you follow these steps and lose money: don't blame me
- no help... Sure, i might try to help you out if you run into problems, but i'm under no obligation to do so. Best effort only, and only when i have time to help you
- no docker. Sure, docker is great, but if you run docker containers, you'll never know what's under the hood . It's easy to download and spin up a docker container, but you'll learn little (or nothing). Don't get me wrong, if you're building your own containers or if you don't want to learn how to setup your service, docker is great... Just not if you want to get your hands dirty
- bitcoin core, c-lightning and RTL are built from source in this walktrough... It's up to you to periodically perform updates (not only for these binaries, but for all packages on your system)
- this tutorial is a work in progress... There are many other steps (hardening, cleanup,...) that could happen. I'll probably edit these steps when i get input, or when i think about something myself. This is also why i split up this thread, this way every step has the chance/space to grow in the future...
Overview Of what we'll be installingBitcoin Core: a full node implementation and wallet, sometimes called the reference client. This node fetches all blocks and unconfirmed transactions from the peers it's connected to, parses and verifies everything and has a full wallet functionality C-lightning: a Lightning Network implementation in C. Create lightning channels, create or pay lightning invoices. RTL: Ride the lightning: one of the best GUI's that can be used on top of an existing c-lightning daemon. No extra functionality, but a lot easyer to use than using lightning-cli
|
|
|
|
~12€ worth of BTC for 10 minutes of my time... Sure... As long as following requirements are met: - I'm payed upfront, or an escrow i trust is being used
- You promised no identifying information... As soon as you ask identifying information (including but not limited to: exact balances, addresses, country, name, exact age,...) i'm walking away and keeping the funds for my troubles
- You realise i'm holding some crypto, I have a technical background, but i'm not a trader... I can't answer any questions i know nothing about
- I won't hold a voice/video call, no insecure clients, no chat clients on your own website, no clients that need KYC to use (including those phone messengers that need to verify your phonenumber),... So basically: send me the questions via mail and i'll type out the answers and reply afterwards
It's friday afternoon, it's 14:20. I get off work at 16:00. If you're interested, set everything up before 15:40 and you'll have your answers before 16:00 |
|
|
|
Thanks for your response.
I hadn't considered using a mixing service.I will do some research on the topic.
Im still having a hard time understanding the 3rd option, At the end i End up with some ZEC in a wallet,
but this still needs to be exchanged for BTC on an exchange? Which would put me back in the same scenario, ie some BTC on an exchange that my identity is linked to?
Or is my understanding wrong in this case?
Seems as if using a mixer is the best option.
Well, there are different trains of tought on the best option... Mixing is defenately the easyest option of the 3... But you'll need to put your trust in the mixing service... If i'm not mistaking Theymos (The admin) isn't a big fan of mixing services for this very reason... What if the mixer is a scam or a honeypot? What if they made mistakes in their security protocol, what if their servers get seized? But, if you trust them, a mixer is a cheap and fast method The 3th option isn't that hard either: You controll unspent outputs funding your address, let's call it 1BtcAddressA. At this point, you go to an (on-the-fly) exchange and exchange your BTC to (for example) XMR (or ZEC or Verge or...). You create an XMR wallet on your hardware wallet (or desktop wallet) and withdraw the XMR to your local wallet (you now have an unspent output on the XMR network funding address 4XmrAddressB). Since this is a high anonimity coin, only the exchange knows they funded 4XmrAddressB. Now, you either create a second new XMR wallet (or a new address within the same wallet if you trust yourself not to start mixing unspent outputs) and you use the unspent output funding 4XmrAddressB to fund 4XmrAddressC. At this point, the link is completely broken. Now, you use a different exchange to exchange the unspent outputs funding 4XmrAddressC on the XMR network for an unspent output on the bitcoin network funding a brand new address on a new wallet ( 1BtcAddressD). At this point the link is completely broken. If you're paranoid, you can perform these steps over Tor and VPN, or you can mix several methods just to be sure... Edit: it's friday, i'm bored, i added a visual aid... Copyright: Me   |
|
|
|
given any one of the addresses I have used people with enough skill(or gov's ect ) could determine my identity?
yes given any one of the addresses I have used people with enough skill could determine my IP Address?
yes What level of skill is required to deduce the information above?
beginner level... You don't even need to know the technical details. The only thing one needs is the ability to follow a very simple input/output trail (or give a couple bucks to one of the many companies that specialise in this) and the power to ask the exchanges you used for the KYC documentation you provided (aka get a court order). Altough, with the security flaws in many of the exchanges, you might not even need the power to ask an exchange for KYC documents, sometimes exchanges are so vulnerable they get hacked and your private information is sold for pennies on the darknet... If my assumption above is true is, how can i regain some Pseudonymity while keeping my current coins?
--snip--
Your coins exist as simple unspent outputs funding addresses you created (or that were created by an online service, altough i discourage storing funds on exchanges or online wallets). They're not physical things. You cannot regain pseudo-anonimity if you want to keep the exact same unspent outputs funding the exact same addresses. BUT: an unspent output x with value y funding address z is worth exactly the same as unspent output a with value y funding address b on the same chain. If you're fine with this concept, you can create a brand new wallet (i prefer a hardware wallet or properly generated paper wallet, but a TRUSTED desktop wallet on a CLEAN PC might work aswell if you don't have enough funds). Then, you can use a mixer, a coinjoin wallet, or exchange your "traceable" coins to a high anonimity currency and back to BTC. Basically: "traceable unspent outputs" => mixer => "output from mixer funding brand new address from brand new wallet" or "traceable unspent outputs" => coinjoin wallet => coinjoin => "output from coinjoin funding brand new address from brand new wallet (or just keep using the coinjoin wallet)" or "traceable unspent outputs" => exchange => high anonimity coin => exchange => "output from exchange funding brand new address from brand new wallet" |
|
|
|
1 - mocacinno Wow, it has been a while since i was last able to participate... I usually notice the thread once all slots have been filled Thanks for the entertainment btw |
|
|
|
|
So, i assume you're either the owner or getting payed by the owner of this wallet, right?
Since there is an online version, is it safe to conclude this is a custodial wallet? If so, the service is in controll of the keys (not the user), so they're the ones in control of the funds... So if it's a custodial wallet, it's actually an exchange disguised as a wallet?
Personally, i wouldn't use a new, unknown wallet... Especially if i have doubts wether the wallet service has access to my private keys. I'd stick to hardware wallets, or at the very least open source wallets that have been community vetted and have a long (positive) history in the community.
EDIT: I just noticed CLOUDFLARE SSL... Really??? A MITM for a potentially custodial wallet service... If your funds get stolen you won't even be able to prove it was the wallet service, it might aswell be a cloudflare employee... A red flag in my book...
|
|
|
|
|
Electrum uses a gap limit. When they detect an address is being funded, it makes sure it derives and monitors the next (gap limit) addresses aswell.
For example, if the gap limit is 50, a new wallet only contains unfunded addresses, so electrum will derive and monitor transactions for the first 50 addresses.
If the first address gets funded, electrum will derive and monitor the first 51 addresses.
If you manually pick and send the 10th address and it gets funded, electrum will derive and monitor the first 61 addresses.
If you create a wallet, change the gap limit to 100, manually pick the 99th address and it gets funded, then decrease the gap limit to 50 and restore the wallet from seed, the funded address will no longer be monitored by electrum untill you've funded address 48 (and because of the gap limit, electrum will now derive and monitor address up untill 99).
|
|
|
|
Electrum with a hardware wallet is fine. Electrum on a wiped and air gapped machine that never sees the internet is fine. I've never understood why anyone recommends any Windows PC based wallet for a connected machine. You never know what'll be hiding.
I Totally AGREE !!! Finally someone that understands this concept. With a non connected memory device to store my Bitcoins, I do not have worry about them ever being removed. This allows me to back up my Seed Words here in the forum, and will never risk losing or forgetting my Seed Words as some people have. In case you were serious and this really is your seed: your wallet is now compromised because you posted a picture of your seed on a public forum.. empty this wallet and never use it again. Anybody can restore your wallet using electrum and sign transactions funding the addresses in this wallet from this point forward. After you emptied this wallet, make sure you also move the funds you might have on the forks (like bch or bsv), the same seed can be used to steal those ones to. |
|
|
|
It's to take payment for a domain. I think the client is part of the scam. I will avoid.
If you're the seller, there should be no need to get lured to an unknown (and potentially scam) exchange. You should just use a trusted wallet (desktop, paper or hardware) on a clean PC to generate an address, the buyer should then fund this address and you should wait untill the transaction funding your address is confirmed before transferring the domain. At no point should you be forced to use an exchange for anything... Don't let your buyer talk you into opening an account on an exchange to receive funds, don't let him talk you into exchanging your funds into fiat on an unknown exchange, don't let him talk you into sending funds to an unknown exchange to "verify" your account. Like i said, use a destkop (electrum, core), hardware (trezor, ledger) or properly generated paper (bitaddress.org => offline) wallet to generate an address and let him fund this address. You shouldn't care where he got the coins, nor should you use an untrusted exchange to exchange your crypto back into fiat (if you wish to do this) |
|
|
|
|
Show Posts
