Trying to update mynode last couple hours and its proving to be beyond my understanding. If anyone's able to help, I'm stuck. Here's the instructions: 1. Start by running myNode on your device via the instructions above in "Running myNode" 2. Clone the latest release from the git repo on your PC or laptop * Run 'git clone https://github.com/mynodebtc/mynode.git --branch latest_release' * Run 'cd mynode' 3. Run 'make rootfs' 4. Run 'make start_file_server' * This will run a local HTTP server so your device can download files 5. On your device, run 'sudo mynode-local-upgrade [dev pc ip address]' * This will download your locally generated artifact and install it on your device * Your device will automatically reboot to ensure updates take effect 6. Optional: Run 'make stop_file_server' * This will stop the local HTTP server 7. You are now running the latest version of myNode software! I'm stuck at #3 Using git bash on windows 10 I get this: user@mycomputer MINGW64 ~/mynode (master) $ make rootfs
bash: make: command not found Not sure what I'm doing wrong Your mistake is using Windows, tools/software make isn't available by default on Windows. I saw people port tool make to Windows, but i don't know if it's stable or still updated. My suggestion is run the guide from linux distro which have live OS feature such as Ubuntu. If you're not sure how to do it, see https://ubuntu.com/tutorials/tutorial-create-a-usb-stick-on-windows |
|
|
|
|
Both @squatter and @pooya87 forget that majority of android smartphones are outdated and don't receive security updates, so even if a vulnerability is found and fixed, most smartphone remain insecure.
Bad people could learn known vulnerability and try to target user with outdated smartphone.
At least Windows and Linux OS got regular update, even though Windows update might break something and update availability on Linux depends on the contributor/company behind it.
|
|
|
|
|
So the idea is swapping Bitcoin with certain stablecoin? It's not bad idea, but it switching the trusted party from centralized exchange/payment processor (which convert BTC to USD automatically) to company/group which issue the stablecoin.
And Tether which used as example have shady reputation.
|
|
|
|
|
Weird, usually it would detect the database and carry out normally (or verify whole blockchain again in very few cases).
Can you share your debug.log file? It's possible the database (blockchain files) got corrupted and Bitcoin Core decided to resync from scratch.
|
|
|
|
-snip-
Alternatively, if you use Ubuntu, you can also install it through the Ubuntu Software. --snip-- Do you know who maintains it? Is it up to date? Other linux "store" such as Snap have very outdated version of Electrum. |
|
|
|
And don't forget to obtain testnet coins, there are many faucets such as Testnet Faucet |
|
|
|
I don't understand why I can't run Wasabi wallet via Turkey's internet connection. Is there anyone who has the similar problem here?
Additional information: I have to select obsf4 bridge to run Tor Browser because Tor is censored in my country.
Do you install Tor on your system? Wasabi Wallet will try to use Tor which is installed on your system, before using Tor which included on Wasabi Wallet. If not, please try install Tor and configure it to use one of obfs4 bridge you know, then try to run Wasabi wallet again. |
|
|
|
IMO it's a bit confusing, usually Archival Full Nodes only means node which store whole blockchain. Can you share reference/discussion which mention "Archival Full Nodes" also means open connection? Are those categories classify types of bitcoin clients only or is it the same with other cryptocurrencies wallets?
Only for Bitcoin and altcoin based on Bitcoin. Few altcoin such as Ethereum have their own classification/definition, for example SPV isn't exist on Ethereum, but there's similar client category which is Light client/node. I want to focus on this category as you have mentioned the exemple of Mycelium client because i always thought it's one of the most secure wallets based on shared nodes like with Electrum. From what i can understand, if the server get compromised, the wallet will not work anymore and the company is the only responsible to make it run again. Right?
Isn't this considered as an important vulnerability?
Web wallet like blockchain.com, is it classified under this category?
If you're talking about Electrum, then no because they use MIT License which comes without any warranty. Most closed source wallet or custodial service have different license / terms and condition though. |
|
|
|
- Tindakan mana yang seharusnya dilakukan oleh otoritas pemerintahan terhadap Bitcoin sitaan? Menahannya seperti Bea Cukai Finlandia atau melelangnya seperti pemerintah AS dan Belgia?
Tergantung kebijakan masing-masing pemerintahan setiap negara. Tetapi menurut saya, seharusnya dilelang, tetapi hanya seseorang yang memiliki reputasi yang baik/positif untuk mengurasi resiko Bitcoin digunakan untuk aktivitas kriminal. 3. Pihak Bea Cukai bisa melacak aktifitas yang dilakukan pembeli terhadap Bitcoin tersebut dari history pada address wallet BTC pembelinya.
Menurut saya kurang efektif karena seseorang bisa menukarkan Bitcoin dengan cryptocurrency lainnya yang memiliki yang lebih baik (contoh: Monero). |
|
|
|
There's no limit to which you can go in that case, which doesn't sound like a long term solution to me...But.. What do i know.
You can use hardware/internet growth when deciding block size increase, BIP 103 ( https://github.com/bitcoin/bips/blob/master/bip-0103.mediawiki) mention such scenario. But this idea bring many question/problem with no universal correct answer/solution : 1. What hardware should be used as reference? Raspberry Pi? Newest Intel/AMD processor? 2. Upper limit of the hardware costs used as reference 3. Should we use slowest/average internet growth as reference 4. What if block size growth is too big to the point HDD I/O speed can't keep up and SSD the only option, which makes storage costs growing quickly (e.g. Ethereum blockchain size which is about 3.8TB and grow about 1.6TB in last year) |
|
|
|
That's the limitation of the HDD, it won't get much faster without using SSD (either to store whole blockchain or only store chainstate folder). Consider upgrading to SSD (SLC: single-level cell type).
SSD which uses SLC isn't easy to find and quite expensive, unless you're talking SSD which uses SLC only for cache/buffer. |
|
|
|
Moving BTC to a 5 minute blockspeed would literally double it's transaction capacity. orphaning rates aside, this is contentious for another reason: it speeds up the emission rate by a factor of 2. those aren't the monetary properties that bitcoiners signed up for. it would also only represent a small, linear increase in throughput capacity. what we need are mechanisms that can provide exponential increases. LN is one such mechanism. Alternatively you could reduce block reward 50% to keep emission rate. But both changing block time interval or block reward require hard-fork, which won't be approved, especially because Bitcoin community prioritize backward compatibility. |
|
|
|
So i've finished download .ova image from https://mynodebtc.com/ and just tried it a bit. 1. By default it asks 4 processor, 4 GB RAM & 27 MB video memory 2. If you use VirtualBox, you need to install VM VirtualBox Extension Pack 3. Guest Additions isn't installed by default, so you must install it by yourself (i haven't tried it yet). 4. myNode uses Debian 10 64-bit with OpenBox desktop environment 5. The default credentials is Username: admin
Password: bolt
6. I don't need to configure anything, but if you need to configure anything (e.g. import Blockchain from your synced node or use Tor), you can't do it from their Web UI and must do it manually. 7. I saw Docker and Fail2Ban installed, even though there aren't images on Docker For now it looks promising, i'll try it later when i'm not too lazy to configure it. |
|
|
|
the list is not new and there is no such thing as "trusted server list" otherwise it would centralize things. what this list is, is that like any other peer to peer application it needs to initially have a list of IP addresses to connect to so that in first attempt it becomes possible to connect to the network. then your client keeps a list and updates it. Additionally, trust isn't equal security. Latest commit which change server.json file shows there was 1 phishing server which is removed. |
|
|
|
|
Technically it's possible, you just need to find wallet software or modify source code of wallet software to hide all generated address which doesn't meet your vanity pattern/rules.
But as other mentioned, computational power to find address which match with desired vanity pattern/rules are the biggest problem which makes the idea isn't practical.
|
|
|
|
Not my topic but question to the people replying to this - what kind of security risks (if any) come with running a full node from your residential connection?
If you decide to contribute to the network, your IP will be visible to everybody. At worst your IP can get DDOS'ed probably but since your router is behind a firewall and only your fullnode will use the port that you forwarded, I don't think there are any serious risks like getting hacked etc... If you only download the data and not upload, it is not risky at all. Ya I figured the most would be DDoS. Is getting DDoS'd while running a full node common in the Bitcoin world? I've run private game servers and it's very common in that world  It rarely happens because there aren't many options to DDoS full nodes. Additionally, Bitcoin Core have mechanism to block peers/nodes who attempt to DDoS by sending invalid information. You probably don't need to worry about it too much, unless your node is part of public service (e.g. pools, block explorer, exchange, etc.) |
|
|
|
|
Show Posts
