For the past year tobtoht and I have been working on the foundations of a new Monero desktop GUI called Feather for Mac OS and Linux platforms (Windows tentative) using Qt5, libwallet, QtWidgets. The goal of this new wallet is to provide a practical, robust and easy-to-use Monero wallet for every day use. It aims to be beginner friendly, but should also cater to the needs of experienced Monero users with the addition of advanced features like coin control and multisig. Feather's user interface is inspired by Bitcoin's Electrum wallet, but adapted to fit Monero. Feather is not a fork of Electrum, all of the UI code was written from scratch in C++ / QtWidgets. Development began in the summer of 2019. We estimate to release a beta version in November or December.
Our primary motivation is to create a wallet that we ourselves would want to use and recommend to friends. There aren't many options when it comes to non-custodial Monero desktop wallets. The CLI is an excellent tool for power-users, but is simply not an option for users that are not familiar with with the terminal. The GUI has a slick user interface, but is demanding on system resources due the use of Qt Quick. Instead we've taken inspiration from Bitcoin's Electrum and started working on the most basic looking Monero desktop wallet one can imagine. We've gotten rid of a lot of functionality, but also added new functionality. Just focussing on the basics results in a clean, robust, and beginner proof wallet.
In an effort to mitigate unintentional off-chain linking, we have made it harder to reuse addresses by automatically hiding used subaddresses. We find that the primary address leads uninformed users to believe that it is somehow functionally incompatible with subaddresses, or that funds sent to subaddresses can not be spent together. To encourage the use of subaddresses the primary address is hidden by default, and only used for change and coinbase outputs. Our wallet supports advanced coin control features like freeze/thaw and sweeping a single output. In the future we may add manual transaction input selection. There is no need to manually setup Tor to protect your traffic, Feather comes bundled with Tor. By default all traffic is routed through Tor with the exception of traffic between wallet and daemon. Wallet synchronization over Tor takes substantially longer than over clearnet, but you can optionally enable to connect to remote nodes over Tor. If your machine already has a Tor daemon running Feather can use the system daemon when instructed. Just like in the official GUI, Feather essentially has 2 modes of connecting to the Monero network. You either host your node somewhere (localhost/LAN/internet) or we'll provide you one from a list of trusted, stable, community hosted remote nodes (like Cake Wallet). If Feather detects that it's running on Tails or Whonix it will automatically connect to a random .onion remote node.
Feather is built with Qt Widgets, providing native looks and performance. In a recent test™ a wallet with 10k+ transactions only consumed 200 MB ram (before optimizations). In comparison, the official GUI uses 400 MB before a wallet is opened. GPU power is plenty nowadays so this hardly a problem, however, we are serious about providing an user interface that feels snappy to use. The application itself starts within 1-2 seconds on most machines (Bitcoin's Electrum is more like 4-5 seconds due to their usage of PyQt).
We have implemented Tevador's 14 word seed scheme with embedded restore height. The same function is used to derive the private view key from the private spendkey, therefore it is possible to convert the 14 word seed into a standard 25 word seed in case you want to restore the wallet using the official wallet software. Feather connects to a websocket server over Tor to obtain miscellaneous data such as: price information, a list CCS proposals, posts on /Monero, the most recent blockheight, a list of community hosted nodes and the latest version of Feather. The websocket server itself is open-source and self-hostable. By default Feather will connect to a server hosted by the project maintainers. The websocket connection can be disabled completely, but some functionality will be disabled/broken. Our target audience are users who want to use Monero without too many issues and we've designed the wallet as such, with lots of convenience features, while routing it all over Tor in the background. The native look of the application should feel familair to users as it behaves like any other program that runs on their computer. Added benefit for future contributors/developers is that it's very fast to implement/test UI components by borrowing from QtWidget's vast library. This in contrast with the Monero GUI, which uses custom QML components - a tricky and time consuming rendereframework more suited for large teams to create electron-like applications.
Feather is able to show detailed transaction and output information including key images, unlock times and ring members.
Support for 2/2 and 2/3 multisig is in the works.
Feather will be distributed as a portable executable.
Feather will ship on Linux and Mac OS - and also Windows once we get static cross compiles to work (rip)
Feather has built-in support for XMR to BTC conversion via XMR.to (no commercial affiliation)
We can easily support additional interfaces other than QtWidgets (like QML for a mobile app, curses, etc) as business logic is stricly seperated from the presentation layer.
Work started early summer 2019. We still have some features to finish, prepare CI/CD, etc. As such we expect an alpha or beta release in December 2020. For this we would like the community's approval to allow the milestones defined in GUI CCS to be used for the remainder of this project, paid in full - we can use the support. Consequently all code will be licensed under the Monero Project and features/changes to libwallet or wallet2 will be committed to upstream (Monero GUI/core). Future development and releases will be maintained by dsc__ and tobtoht.
Idle in #feather on irc.oftc.net if you want to help beta testing in a month or so. You will need Linux, as this is our primary platform for developing the application. Please let us know what you think in the comments. We're open to suggestions/feature requests/brainfarts.
Hice nmap en imss.gob.mx. Esta mas abierto que el OXXO. Ni siquiera funciona el SSL es una burla
PLS no me baneen Aqui para los curiosos Starting Nmap 7.60 ( https://nmap.org ) at 2020-09-01 03:06 CDT Nmap scan report for imss.gob.mx (220.127.116.11) Host is up (0.060s latency). Other addresses for imss.gob.mx (not scanned): 18.104.22.168 Not shown: 740 filtered ports PORT STATE SERVICE 53/tcp open domain 80/tcp open http 81/tcp open hosts2-ns 82/tcp open xfer 83/tcp open mit-ml-dev 84/tcp open ctf 85/tcp open mit-ml-dev 88/tcp open kerberos-sec 89/tcp open su-mit-tg 90/tcp open dnsix 99/tcp open metagram 389/tcp open ldap 443/tcp open https 444/tcp open snpp 445/tcp open microsoft-ds 500/tcp open isakmp 554/tcp open rtsp 555/tcp open dsf 587/tcp open submission 631/tcp open ipp 636/tcp open ldapssl 777/tcp open multiling-http 800/tcp open mdbs_daemon 801/tcp open device 843/tcp open unknown 880/tcp open unknown 888/tcp open accessbuilder 990/tcp open ftps 995/tcp open pop3s 999/tcp open garcon 1000/tcp open cadlock 1002/tcp open windows-icfw 1024/tcp open kdm 1025/tcp open NFS-or-IIS 1028/tcp open unknown 1080/tcp open socks 1111/tcp open lmsocialserver 1234/tcp open hotline 1433/tcp open ms-sql-s 1443/tcp open ies-lm 1455/tcp open esl-lm 1494/tcp open citrix-ica 1521/tcp open oracle 1935/tcp open rtmp 1971/tcp open netop-school 1972/tcp open intersys-cache 1974/tcp open drp 1984/tcp open bigbrother 2000/tcp open cisco-sccp 2001/tcp open dc 2006/tcp open invokator 2020/tcp open xinupageserver 2022/tcp open down 2048/tcp open dls-monitor 2049/tcp open nfs 2065/tcp open dlsrpn 2068/tcp open avocentkvm 2100/tcp open amiganetfs 2200/tcp open ici 2222/tcp open EtherNetIP-1 2557/tcp open nicetec-mgmt 3000/tcp open ppp 3001/tcp open nessus 3003/tcp open cgms 3005/tcp open deslogin 3006/tcp open deslogind 3007/tcp open lotusmtap 3011/tcp open trusted-web 3013/tcp open gilatskysurfer 3017/tcp open event_listener 3030/tcp open arepa-cas 3052/tcp open powerchute 3071/tcp open csd-mgmt-port 3077/tcp open orbix-loc-ssl 3306/tcp open mysql 3333/tcp open dec-notes 3389/tcp open ms-wbt-server 3404/tcp open unknown 3551/tcp open apcupsd 3580/tcp open nati-svrloc 4000/tcp open remoteanything 4001/tcp open newoak 4002/tcp open mlchat-proxy 4343/tcp open unicall 4443/tcp open pharos 4444/tcp open krb524 4445/tcp open upnotifyp 4449/tcp open privatewire 4848/tcp open appserv-http 5000/tcp open upnp 5001/tcp open commplex-link 5002/tcp open rfe 5003/tcp open filemaker 5004/tcp open avt-profile-1 5009/tcp open airport-admin 5050/tcp open mmcc 5051/tcp open ida-agent 5060/tcp open sip 5061/tcp open sip-tls 5080/tcp open onscreen 5100/tcp open admd 5120/tcp open barracuda-bbs 5222/tcp open xmpp-client 5225/tcp open hp-server 5226/tcp open hp-status 5269/tcp open xmpp-server 5280/tcp open xmpp-bosh 5440/tcp open unknown 5500/tcp open hotline 5544/tcp open unknown 5555/tcp open freeciv 5900/tcp open vnc 5901/tcp open vnc-1 5902/tcp open vnc-2 5903/tcp open vnc-3 5904/tcp open unknown 5906/tcp open unknown 5907/tcp open unknown 5910/tcp open cm 5911/tcp open cpdlc 5915/tcp open unknown 5987/tcp open wbem-rmi 5988/tcp open wbem-http 5989/tcp open wbem-https 5998/tcp open ncd-diag 5999/tcp open ncd-conf 6000/tcp open X11 6001/tcp open X11:1 6002/tcp open X11:2 6003/tcp open X11:3 6004/tcp open X11:4 6005/tcp open X11:5 6006/tcp open X11:6 6007/tcp open X11:7 6009/tcp open X11:9 6100/tcp open synchronet-db 6510/tcp open mcer-port 6543/tcp open mythtv 6565/tcp open unknown 6580/tcp open parsec-master 6666/tcp open irc 6699/tcp open napster 6779/tcp open unknown 6789/tcp open ibm-db2-admin 7000/tcp open afs3-fileserver 7001/tcp open afs3-callback 7002/tcp open afs3-prserver 7004/tcp open afs3-kaserver 7007/tcp open afs3-bos 7070/tcp open realserver 7100/tcp open font-service 7443/tcp open oracleas-https 7777/tcp open cbt 7778/tcp open interwise 7999/tcp open irdmi2 8000/tcp open http-alt 8001/tcp open vcom-tunnel 8002/tcp open teradataordbms 8007/tcp open ajp12 8008/tcp open http 8009/tcp open ajp13 8010/tcp open xmpp 8011/tcp open unknown 8021/tcp open ftp-proxy 8022/tcp open oa-system 8031/tcp open unknown 8042/tcp open fs-agent 8045/tcp open unknown 8080/tcp open http-proxy 8081/tcp open blackice-icecap 8082/tcp open blackice-alerts 8083/tcp open us-srv 8084/tcp open unknown 8085/tcp open unknown 8086/tcp open d-s-n 8087/tcp open simplifymedia 8088/tcp open radan-http 8089/tcp open unknown 8090/tcp open opsmessaging 8093/tcp open unknown 8099/tcp open unknown 8100/tcp open xprint-server 8180/tcp open unknown 8181/tcp open intermapper 8192/tcp open sophos 8193/tcp open sophos 8194/tcp open sophos 8200/tcp open trivnet1 8222/tcp open unknown 8300/tcp open tmi 8333/tcp open bitcoin 8383/tcp open m2mservices 8402/tcp open abarsd 8443/tcp open https-alt 8500/tcp open fmtp 8600/tcp open asterix 8701/tcp open unknown 8800/tcp open sunwebadmin 8873/tcp open dxspider 8888/tcp open sun-answerbook 8899/tcp open ospf-lite 9000/tcp open cslistener 9001/tcp open tor-orport 9002/tcp open dynamid 9003/tcp open unknown 9009/tcp open pichat 9010/tcp open sdr 9011/tcp open unknown 9040/tcp open tor-trans 9050/tcp open tor-socks 9071/tcp open unknown 9080/tcp open glrpc 9081/tcp open unknown 9090/tcp open zeus-admin 9091/tcp open xmltec-xmlmail 9099/tcp open unknown 9100/tcp open jetdirect 9101/tcp open jetdirect 9102/tcp open jetdirect 9103/tcp open jetdirect 9110/tcp open unknown 9111/tcp open DragonIDSConsole 9200/tcp open wap-wsp 9207/tcp open wap-vcal-s 9220/tcp open unknown 9500/tcp open ismserver 9943/tcp open unknown 9998/tcp open distinct32 9999/tcp open abyss 10000/tcp open snet-sensor-mgmt 10001/tcp open scp-config 10002/tcp open documentum 10003/tcp open documentum_s 10004/tcp open emcrmirccd 10009/tcp open swdtp-sv 10010/tcp open rxapi 10012/tcp open unknown 10024/tcp open unknown 10025/tcp open unknown 10082/tcp open amandaidx 11110/tcp open sgi-soap 12174/tcp open unknown 12265/tcp open unknown 12345/tcp open netbus 15002/tcp open onep-tls 16000/tcp open fmsas 16001/tcp open fmsascon 16012/tcp open unknown 16016/tcp open unknown 16018/tcp open unknown 16080/tcp open osxwebadmin 18040/tcp open unknown 18101/tcp open unknown 20000/tcp open dnp 30000/tcp open ndmps 31337/tcp open Elite 50000/tcp open ibm-db2 50001/tcp open unknown 55055/tcp open unknown 60443/tcp open unknown Nmap done: 1 IP address (1 host up) scanned in 3.34 seconds En serio de milagro nadie les ha hecho nada
Sorry if this is a boring or redundant topic, but I just can't find an answer. This is my first attempt at a Monero transaction. I downloaded and installed the Monero Windows GUI app. I handled the antivirus issues, and the network is showing as connected, with both Daemon and Wallet synchronized. I used Changelly to exchange Bitcoin to XMR from a Coinbase account. The transaction seemed to work smoothly, and Changelly is telling me the funds have been moved successfully. My Monero wallet does not show any received funds. When I compare the wallet's primary address and the address listed in the confirmed transaction, the appear identical. What could have possibly gone wrong? How do I debug this?
Evo uses Proof of Stake consensus mechanism, which is different from Bitcoin's PoW (Proof of Work). Evo mining process in PoS system is called staking. The block producer will get 6.5EVO, as well as the transaction fees and gases as block reward. So the real reward is usually more than 6.5 evo in total. Basic requirements for staking：
Run a Coinevo fullnode, and keep online (Since Coinevo is using PoS, we don't need any mining machine, just PC or even Raspberry Pi can run a fullnode);
Have some EVO in the wallet (fullnode)（Any amount of EVO can be used for staking, more EVO means higher possibility to stake).
If you have no EVO yet, please get some from market before you doing following staking settings. Currently, Coinevo Core wallet is the only wallet that support Coinevo PoS staking. Note that other wallets like mobile wallet and Evo Electrum are not able to stake for the time being. Two ways to stake:
Method 1：Staking with evod, using command line, suitable for Linux/OSX/Windows/Raspberry Pi users who are familiar with command line tools.
Method 2：Staking with evo-qt wallet, with GUI, suitable for common users.
Either way works in the same way for staking, so you can choose either method you like.
Method 1：Staking with evod (command line)
1. Run evod
Follow the guidance to run evod :
Staking is default on for evod, so no need for other options if you only want to stake.
2. Send some EVO to your wallet
First you can generate a new address with：
This will generate a new address with Prefix '1'. You can send some EVO to this new generated address for staking. You can generate as many addresses as you like, and send arbitrary EVO as you like for staking. Note：The coin should wait for 500 blocks before being able to stake, i.e. about 17 to 24 hours to MATURE.. After the EVO node syncing to the latest block, you can check current balance with ./evo-cli getbalance or get utxo list with./evo-cli listunspent Please do following steps after your coin is mature.
enabled means if your wallet have enabled staking, it should be true by default. staking means if your wallet is currently staking (mining). weight stands for the amount of EVO that is staking right now, with unit 10^-8EVO, here in the example, we have 0.532EVO staking. expectedtime stands for the expected time that you will get a reward, the unit is second.
4. How to stake if the wallet is encrypted？
If your wallet is not encrypted, you can skip this section. However, for security, we recommand you encrypt your wallet. Coinevo wallet can be encrypted with encryptwallet . However, staking will be stopped when it is encrypted. For example, ./evo-cli getstakinginfo for a encrypted wallet：
See staking turns to false , which means wallet is not staking. You can use walletpassphrase to unlock wallet for staking：
./evo-cli walletpassphrase "" 99999999 true
After unlocking, you can double check getstakinginfo , it should look the same with previous unlocked result, staking become true.
Method 2: Staking with evo-qt wallet (official PC wallet)
Current supported platform: Mac/Linux/Windows.
1. Open Evo qt wallet
Launch the wallet.
2. Send some EVO to your wallet
If you already have some EVO in your wallet, you might skip this step. Note：The coin should wait for 500 blocks before being able to stake, i.e. about 17 to 24 hours to MATURE..
3. Check staking status
The flash sign at the bottom of wallet shows staking info : Solid black flash means it is staking now. For more information, you can put your mouse on the flash, e.g.:
Staking : if it is staking；
Your weight is : How many EVO are able to used for staking, unit is EVO;
Network weight is : How many EVO are staking in the network, unit is EVO；
Expected time : expected time to get reward, unit is Day.
Hollow flash measn it is not staking Possible reasons for not staking：
1.There is no coins of no mature coins (more than 500 confirmations(blocks)) -- Solution: send some EVO to the wallet and wait for 500 blocks (about 17 hours);
2.Wallet is locked/encrypted -- Solution: unlock the wallet for staking.
No flash sign means staking is disabled
3.Staking is disabled -- Solution: enable staking in the evo.conf (-staking=true)
About block reward
The block producer will get more than 6.5 EVO rewards, something to keep in mind:
The reward come from a new transaction, you can check balance to see if you get the reward.
Once succesfully stake, you will get 0.65EVO reward immediately.
Other 5.85EVO will be sent to you after 500 blocks (about 17 or 24 hours), in continuous 9 blocks, within each block you will get 0.65EVO,, so in total it will be 5.85EVO.
The staked coins (UTXO) will be locked for 500 blocks, during this period, it cannot be spent nor be used to stake.
How to disable staking?
Staking is by default enabled for Coinevo wallet. If you need to disable staking for some reason (for example exchanges are always recommanded to disable staking), you might following anyone of the 3 ways below: 1 Add -staking=false when running Coinevo node：
./evod -staking=false -daemon
For qt wallet, it is like：
2 Add config staking=false in evo.conf; 3 Encrypt wallet, since encrypted wallet will automatically stop staking.
Reddcoin (RDD) Core Wallet v3.0.1 - January 09, 2020 Version 3.0.1 is the official release version of Reddcoin Core. It is available for download at Reddcoin Core's Github repository here: https://github.com/reddcoin-project/reddcoin/releases/tag/v3.0.1 This release features PoSV v2.supermajority activation and new staking ruleset (and minor misc fixes). v3.0.1 is still not yet MacOS Catalina compatible. We are still working and should have that fix issued very soon. Sincere apologies to our Mac-using ReddHeads. It is particularly important that all users upgrade, as once PoSV v2 is enforced, version 4 blocks will be rejected from the network entirely. Therefore v3.0.1 is a "strongly recommended" update for all users. Note: If you have already installed v3.0.0, this upgrade is not required. If you have not yet upgraded from v2.0.x or earlier, this is a REQUIRED upgrade. Please install the newest version v3.0.1 to avoid losing functionality during supermajority activation of PoSV v2. Reddcoin Core version 3.0.1 is now available from: https://github.com/reddcoin-project/reddcoin/releases Release Notes are available here and replicated below in this announcement: https://github.com/reddcoin-project/reddcoin/blob/mastedoc/release-notes.md This is a new major version release of Reddcoin. Previously, the original and subsequent versions of Reddcoin were taken from a fork of the Litecoin code base. With the release of Reddcoin V2.0.0, the code was based directly from a fork of Bitcoin. This allows for better source control and feature implementation from upstream changes into the future With the release of Reddcoin V3.0.0, the PoSV stake reward has been improved to allow for a target 5% network growth, in process re-incentivizing individual network stakers and providing for integrated dev support. Upgrading to this release is strongly recommended and required for continued operation. Once a supermajority of 90% is reached, old wallets will no longer accept the new v5 blocks. Please report bugs using the issue tracker at github: https://github.com/reddcoin-project/reddcoin/issues How to Upgrade If you are running an older version of Reddcoin, shut it down. Wait until it has completely shut down (which may take a few minutes for older versions). Run the installer (on Windows) or just copy over /Applications/Reddcoin-Qt (on Mac) or reddcoind/reddcoin-qt (on Linux). Start wallet. All done!
Reddcoin v3.0.0 introduced an updated PoSV method to better distribute staking rewards and target a overall 5% network growth. Staking and relay policy enhancements
To implement PoSV v2, Reddcoin Core's block templates are now for version 5 blocks only. When PoSV v2 consensus (Supermajority 9000/10000) is reached, only v5 blocks will be accepted by the network.This equates to approximately 90% of blocks being generated over 1 week period. Status at any time may be viewed in node debug.log Blockchain Download: Blockchain data for both testnet and mainnet along with instructions can be downloaded from github. https://github.com/reddcoin-project/bootstrap_files 3.0.1 changelog *83e212838 - John Nash, 2020-01-09 : really delete these files *3a1458ecd - Oliver Webb, 2020-01-08 : Added missing dependency libminiupnpc-dev for Jessie *d21915431 - Tiago Peralta, 2019-06-21 : Add vout to listtransactions/gettransaction *8d58ea7cf - Oliver Webb, 2020-01-08 : Script for downloading pre compiled binaries for Raspbian Jessie, Stretch or Buster *d4eced1bc - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_stretch.sh *c5e9f91cf - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_jessie.sh *5d5771b00 - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_buster.sh *75c6ae91b - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *54c501787 - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *acb30a2b6 - Oliver Webb, 2020-01-05 : script files for Raspbian Jessie (also Stakebox) *cfddbe594 - John Nash, 2020-01-05 : Update copyright year and version *e46e5e7de - John Nash, 2020-01-05 : download script for pre compiled wallet *37386790a - John Nash, 2020-01-05 : change libssl deb packages links to github *9dbc772e6 - Oliver Webb, 2020-01-03 : download script for pre compiled wallet *857d697fd - Oliver Webb, 2020-01-03 : change libssl deb packages links to github *2cb74b9a8 - John Nash, 2019-12-31 : update copyright year *c641a1ab3 - Oliver Webb, 2019-12-30 : Raspberry Pi build script files for v3 wallet *a3f21a4a4 - John Nash, 2019-12-30 : add install script for building db4 update instructions for unix, osx, arm building using the db4 install script *5f6299b2a - John Nash, 2019-12-28 : docs: Update build notes for arm processors *465716c01 - John Nash, 2019-12-28 : test for arm devices *3fec3a535 - John Nash, 2018-02-02 : build: update source paths *5f6031ab4 - John Nash, 2019-12-28 : Scrypt n=1024 Pow hash based upon Colin Percival's Tarnsnap (2009) Modified by Artforz, coblee, pooler, wtogami, Nikolay Belikov, reddink *2fd4d91a0 - John Nash, 2019-12-24 : update copyright year *326828b36 - John Nash, 2019-12-24 : set release state true *8ebede0a6 - John Nash, 2019-12-24 : release notes *36df6fdfb - John Nash, 2019-12-23 : add check explictly for v5 blocks or greater *874dc1f0c - John Nash, 2019-12-17 : remove hardcoded global variable rearrange debug log output *763b25db8 - John Nash, 2019-12-17 : move copyright to new line *536baf635 - John Nash, 2019-12-17 : update version and set release state to false *cde9009f3 - John Nash, 2019-12-17 : update copyright year *ae41b7ed3 - John Nash, 2019-12-17 : set isSuperMajority to 90% for mainnet *e43e1c8ed - John Nash, 2019-12-10 : additional logging to verify isSuperMajority in the debug.log output *e31783cac - John Nash, 2019-12-05 : add/update public key for mainnet *405c6f002 - John Nash, 2019-12-05 : add log output for current inflation rate *9cc43c3f7 - John Nash, 2019-12-02 : determine calculated stake based on posv version *7baa3bf75 - John Nash, 2019-11-25 : check the posv transaction for correct pubkey *9ffa7ca38 - John Nash, 2019-11-21 : check for posv v1 or posv v2 blocks when calculating stake reward *39f7aad68 - John Nash, 2019-11-14 : add logging *0e283e6c3 - John Nash, 2019-11-13 : correct maths *74cbdeffd - John Nash, 2019-11-11 : use new posv v2 functions addidtional logging *35d7413b5 - John Nash, 2019-11-11 : add new proofofstakereward *3d917216c - John Nash, 2019-11-11 : get inflation adjustment *f63d17443 - John Nash, 2019-11-08 : add the developer output split fund output *ca263c9c9 - John Nash, 2019-11-05 : add dev key to chainparams *df6996ab0 - John Nash, 2019-11-05 : add block version checking *14b663479 - John Nash, 2019-11-05 : increase block version Credits Thanks to everyone who contributed to coding, testing and feedback for this release, notably:
AMA/Tutorial: Run a full node on AWS free tier with local LAN storage
This is a tutorial/AMA on how you can be running a full node, in the AWS cloud, for very low cost or even free. I used to run a node on my local network but there is a problem with this; your public IP is broadcast, and then it gets associated with Bitcoin. Node owners are likely to own Bitcoin, and this raises your personal threat profile, validated against my IDS/IPS logs. Run a VPN? Many VPNs are automatically blocked, or sketchy. Tor is also blocked on a large portion of the internet. Neither provide you with a real static IP, and that helps out the network. There is a easy solution to this; run a node on the AWS free tier, and use an elastic IP so you have a static address. Bandwidth is free in, and low cost out, and you can control how much of that you use easily, and control your spent. The problem is that Amazon charges a LOT for online storage and even with a 1MB blocksize, the blockchain is very large and growing steadily! We mitigate this by using a VPN back to your network, where you can store the blockchain on a SMB share. It is not complicated to do, but there are very many moving pieces to keep track of and configure. In order to fully trust your node, the best way is to build it from scratch. This is my goal in walking you through the process. There are lots of ways to accomplish this same task; I only want to present one that works, and you can go from there. Once you have access to the blockchain in the cloud for reasonable prices, you can also look at things like the Lightning Network. This article makes four major assumptions:
That you have a OpenVPN server on your network and know how to configure it. I use pfSense and OpenVPN; others will work just as well, but you'll need to do a little work to figure out the particulars. If you don't know how, do not fret! There are loads of good tutorials for just about every platform. Or ask below. I also limited the user with access to the share at the firewall specifically to the IP hosting the share to lower the threat envelope.
That you have the blockchain downloaded locally and reasonably up to date. If you don't, head on over to bitcoin.org and download it for OSX or Windows or Linux, whatever you use for your workstation. Follow the directions to set up the software and download/synchronize it to the network. This will take awhile! Once you've synchronized, copy the data directory to your SMB share you want the AWS instance to access. You could also synchronize everything directly on AWS too, but it will likely take longer and may cost a bit for the bandwidth.
That you're on windows. OSX and Linux will have slightly different processes to connect to the instance via the terminal and SSH. If you need help, ask, and I am sure we can get you fixed up.
With that, on with the show! First: Head on over to https://aws.amazon.com/ and make yourself an account. Once you've set up you'll need to start the process of creating a virtual machine on AWS. Look for this graphic and click on it: Start by launching a new machine Follow the rabbit hole, and you'll be looking to create a plain jane Amazon AMI Linux instance. It looks like this: Pick the basic AMI instance Keep in mind you want to pick the x86 version, which is the default. Continue clicking, you'll want to select the t2.micro instance that is eligible for the free tier for new accounts. Pick the free tier. You can also upgrade to the smaller tier for more ram, but the micro works for now. Now, you're going to need a way to connect to your soon-to-be-created node in the cloud. Amazon uses SSH keys to do this, so the next step means you're going to make some. You need to save this file, as if you lose it, you won't be able to access your node anymore. Much like your wallet private keys! Beware losing your keys! If you've made it this far, you're almost launched! Now we need to convert the key to a format that we can use to connect to the instance from Windows. I recommend using Putty! https://www.putty.org/ if you don't have it already; if you're on OSX or Linux, you likely have what you need already. Follow the guide here to get connected: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html Next you'll need to set up a opening in the firewall if you want incoming connections. This is done by adding to the security group in the "Network and Security" section; edit it to look like this: Change the inbound security rules for the instance to accept incoming connections on 8333. The hard part is over! Optional: Configuring a static IP. Amazon calls their implementation "elastic" IPs, but it's really a static IP that you can move around between instances very easily. It will ensure your public address on AWS does not change; it isn't required, but it is better if you intend on allowing outgoing connections. Go back to the main dashboard display. In "Network and Security", click on "Elastic IPs". Select Allocate New Address (blue button on top) and then select it in the table. In actions, you will see "Associate Address". Select this then assign the address to the instance you have previously configured. Done! Next up: Log into your machine, and immediately update everything. Use the IP provided by Amazon, or the Elastic IP if you assigned one to the instance in the last step. type: "sudo yum update" Now, let's get the VPN configured. First step is to install OpenVPN. We need to install the extended package library to do this. type: "sudo amazon-linux-extras install epel" type: "sudo yum-config-manager --enable epel" Now you can install OpenVPN. type: "sudo yum install openvpn" You will need your credential file from OpenVPN; it's a file you generate that will have a .ovpn extension. But you're going to need to upload it to the instance. You can do this through the scp command on OSX or Linux, but if you're on Windows, you'll need another utility. Get WinSCP here: https://winscp.net/eng/download.php But we'll have to tell it where your key file is so you can login. Select "New Session", then use the same IP and username as you did to connect before. We'll need to tell it about the key file though! Select the "Advanced" tab then under the SSH section, click on "Authentication" and then select your private key file you generated in the tutorial above. Connect and upload the .ovpn file that you generated when you added a user for the VPN. This step depends on your OpenVPN configuration - ask below if you have problems. Next, let's verify we can connect to the VPN! type: "openvpn --config my-configuration-file-made-by-openvpn.ovpn &" You will be prompted for a password if you configured one. Verify operation by pinging your LAN router, e.g. type: "ping 192.168.2.1" or the address of the SMB server where you shared the information. Allllrighty! Next up is getting connected to your blockchain. Create a directory where the data directory will be mounted. type: "mkdir blockchain" We need to install samba and some utilities to get things mounted. type: "sudo yum install samba" type: "sudo yum install cifs-utils" Now let's mount the folder: type: "sudo mount -t cifs //192.168.2.100/Bitcoin ./blockchain -o user=bitcoin,vers=2.0,uid=ec2-user,gid=ec2 user,file_mode=0777,dir_mode=0777" Where " //192.168.2.100/Bitcoin" is the address of the SMB server and share where you put the data directory from your initial sync. If you didn't, and just want to sync everything from AWS, then make sure it's a folder where your user has access. In this case, I'm assuming you've made a SMB user with the name "Bitcoin". The command will prompt you for the password to access the share. The other bits ensure you can have read and write access to the share once it's mounted in AWS. Now we're ready for some Bitcoin! Props to the tutorial here: https://hackernoon.com/a-complete-beginners-guide-to-installing-a-bitcoin-full-node-on-linux-2018-edition-cb8e384479ea But I'll summarize for you: Download and then re-upload with WinSCP, or download directly to your instance with wget, the most current Bitcoin core. In this case, it's bitcoin-0.18.0-i686-pc-linux-gnu.tar.gz downloaded from https://bitcoin.org/en/bitcoin-core/. Let's verify it hasn't been tampered with once you have it uploaded to the terminal: type: "sha256sum bitcoin-0.18.0-i686-pc-linux-gnu.tar.gz" Then compare that with the hash value that's listed in the SHA256SUMS.asc file on bitcoin.org. In this case, "36ce9ffb375f6ee280df5a86e61038e3c475ab9dee34f6f89ea82b65a264183b" all matches up, so we know nobody has done anything evil or nefarious to the file. Unzip the file: type: "tar zxvf bitcoin-0.18.0-i686-pc-linux-gnu.tar.gz" There is a warning about a symbolic link; everything seems to work OK regardless, but if anyone knows what or how to fix, please comment. We'll need to get some missing libraries before we can run it; these aren't in the basic AMI instance. type: "sudo yum install glibc.i686" type: "yum install libgcc_s.so.1" FINALLY! We are ready to launch the program. Go to the "bin" directory inside where you unzipped the Bitcoin Core tarball. (e.g. /home/ec2-useblockchain/bitcoin-0.18.0/bin) ./bitcoind -datadir=/home/ec2-useblockchain/data You will see the program either start to sync and download, or start to read the existing blockchain file that you put in the share from before. Congrats! There are a couple extra steps to have it automatically start on reboot, but let's see if anyone gets this far first. I use the "screen" program to do this, but there's also a daemon mode, and some other functionality that is discussed in the hackernoon tutorial. The primary cost will be outgoing bandwidth. AWS charges $0.10/GB beyond 15GB; You can limit the outgoing bandwidth easily according to your budget: https://bitcoin.org/en/full-node#reduce-traffic Hope this encourages people to try running a free, or very low cost, cloud node, with a substantially reduced threat profile.
Hey there, I've got a Windows server and am trying to get a pool going on it, but I'm stuck at the daemon. All the documentation on it only talks about compiling the daemon on linux. Is there a way to get the daemon compiled and running on Windows? Thanks in advance.
Lastupdated2018-01-29 This post is a collaboration with the Bitcoin community to create a one-stop source for Lightning Network information. There are still questions in the FAQ that are unanswered, if you know the answer and can provide a source please do so!
Lightning Network White Paper - The protocol has changed since this original paper, but covers the mid-level mechanics of the Lightning Network with an emphasis on the smart contracts that make it trustless
If you can answer please PM me and include source if possible. Feel free to help keep these answers up to date and as brief but correct as possible
Is Lightning Bitcoin?
Yes. You pick a peer and after some setup, create a bitcoin transaction to fund the lightning channel; it’ll then take another transaction to close it and release your funds. You and your peer always hold a bitcoin transaction to get your funds whenever you want: just broadcast to the blockchain like normal. In other words, you and your peer create a shared account, and then use Lightning to securely negotiate who gets how much from that shared account, without waiting for the bitcoin blockchain.
Is the Lightning Network open source?
Yes, Lightning is open source. Anyone can review the code (in the same way as the bitcoin code)
Who owns and controls the Lightning Network?
Similar to the bitcoin network, no one will ever own or control the Lightning Network. The code is open source and free for anyone to download and review. Anyone can run a node and be part of the network.
I’ve heard that Lightning transactions are happening “off-chain”…Does that mean that my bitcoin will be removed from the blockchain?
No, your bitcoin will never leave the blockchain. Instead your bitcoin will be held in a multi-signature address as long as your channel stays open. When the channel is closed; the final transaction will be added to the blockchain. “Off-chain” is not a perfect term, but it is used due to the fact that the transfer of ownership is no longer reflected on the blockchain until the channel is closed.
Do I need a constant connection to run a lightning node?
Not necessarily, Example: A and B have a channel. 1 BTC each. A sends B 0.5 BTC. B sends back 0.25 BTC. Balance should be A = 0.75, B = 1.25. If A gets disconnected, B can publish the first Tx where the balance was A = 0.5 and B = 1.5. If the node B does in fact attempt to cheat by publishing an old state (such as the A=0.5 and B=1.5 state), this cheat can then be detected on-chain and used to steal the cheaters funds, i.e., A can see the closing transaction, notice it's an old one and grab all funds in the channel (A=2, B=0). The time that A has in order to react to the cheating counterparty is given by the CheckLockTimeVerify (CLTV) in the cheating transaction, which is adjustable. So if A foresees that it'll be able to check in about once every 24 hours it'll require that the CLTV is at least that large, if it's once a week then that's fine too. You definitely do not need to be online and watching the chain 24/7, just make sure to check in once in a while before the CLTV expires. Alternatively you can outsource the watch duties, in order to keep the CLTV timeouts low. This can be achieved both with trusted third parties or untrusted ones (watchtowers). In the case of a unilateral close, e.g., you just go offline and never come back, the other endpoint will have to wait for that timeout to expire to get its funds back. So peers might not accept channels with extremely high CLTV timeouts. -- Source
What Are Lightning’s Advantages?
Tiny payments are possible: since fees are proportional to the payment amount, you can pay a fraction of a cent; accounting is even done in thousandths of a satoshi. Payments are settled instantly: the money is sent in the time it takes to cross the network to your destination and back, typically a fraction of a second.
Does Lightning require Segregated Witness?
Yes, but not in theory. You could make a poorer lightning network without it, which has higher risks when establishing channels (you might have to wait a month if things go wrong!), has limited channel lifetime, longer minimum payment expiry times on each hop, is less efficient and has less robust outsourcing. The entire spec as written today assumes segregated witness, as it solves all these problems.
Can I Send Funds From Lightning to a Normal Bitcoin Address?
No, for now. For the first version of the protocol, if you wanted to send a normal bitcoin transaction using your channel, you have to close it, send the funds, then reopen the channel (3 transactions). In future versions, you and your peer would agree to spend out of your lightning channel funds just like a normal bitcoin payment, allowing you to use your lightning wallet like a normal bitcoin wallet.
Can I Make Money Running a Lightning Node?
Not really. Anyone can set up a node, and so it’s a race to the bottom on fees. In practice, we may see the network use a nominal fee and not change very much, which only provides an incremental incentive to route on a node you’re going to use yourself, and not enough to run one merely for fees. Having clients use criteria other than fees (e.g. randomness, diversity) in route selection will also help this.
What is the release date for Lightning on Mainnet?
Would there be any KYC/AML issues with certain nodes?
Nope, because there is no custody ever involved. It's just like forwarding packets. -- Source
What is the delay time for the recipient of a transaction receiving confirmation?
Furthermore, the Lightning Network scales not with the transaction throughput of the underlying blockchain, but with modern data processing and latency limits - payments can be made nearly as quickly as packets can be sent. -- Source
How does the lightning network prevent centralization?
How would the lightning network work between exchanges?
Each exchange will get to decide and need to implement the software into their system, but some ideas have been outlined here: Google Doc - Lightning Exchanges Note that by virtue of the usual benefits of cost-less, instantaneous transactions, lightning will make arbitrage between exchanges much more efficient and thus lead to consistent pricing across exchange that adopt it. -- Source
How do lightning nodes find other lightning nodes?
Does every user need to store the state of the complete Lightning Network?
According to Rusty's calculations we should be able to store 1 million nodes in about 100 MB, so that should work even for mobile phones. Beyond that we have some proposals ready to lighten the load on endpoints, but we'll cross that bridge when we get there. -- Source
Would I need to download the complete state every time I open the App and make a payment?
No you'd remember the information from the last time you started the app and only sync the differences. This is not yet implemented, but it shouldn't be too hard to get a preliminary protocol working if that turns out to be a problem. -- Source
What needs to happen for the Lightning Network to be deployed and what can I do as a user to help?
Lightning is based on participants in the network running lightning node software that enables them to interact with other nodes. This does not require being a full bitcoin node, but you will have to run "lnd", "eclair", or one of the other node softwares listed above. All lightning wallets have node software integrated into them, because that is necessary to create payment channels and conduct payments on the network, but you can also intentionally run lnd or similar for public benefit - e.g. you can hold open payment channels or channels with higher volume, than you need for your own transactions. You would be compensated in modest fees by those who transact across your node with multi-hop payments. -- Source
Is there anyway for someone who isn't a developer to meaningfully contribute?
Sure, you can help write up educational material. You can learn and read more about the tech at http://dev.lightning.community/resources. You can test the various desktop and mobile apps out there (Lightning Desktop, Zap, Eclair apps). -- Source
Do I need to be a miner to be a Lightning Network node?
Do I need to run a full Bitcoin node to run a lightning node?
lit doesn't depend on having your own full node -- it automatically connects to full nodes on the network. -- Source LND uses a light client mode, so it doesn't require a full node. The name of the light client it uses is called neutrino
How does the lightning network stop "Cheating" (Someone broadcasting an old transaction)?
Upon opening a channel, the two endpoints first agree on a reserve value, below which the channel balance may not drop. This is to make sure that both endpoints always have some skin in the game as rustyreddit puts it :-) For a cheat to become worth it, the opponent has to be absolutely sure that you cannot retaliate against him during the timeout. So he has to make sure you never ever get network connectivity during that time. Having someone else also watching for channel closures and notifying you, or releasing a canned retaliation, makes this even harder for the attacker. This is because if he misjudged you being truly offline you can retaliate by grabbing all of its funds. Spotty connections, DDoS, and similar will not provide the attacker the necessary guarantees to make cheating worthwhile. Any form of uncertainty about your online status acts as a deterrent to the other endpoint. -- Source
How many times would someone need to open and close their lightning channels?
You typically want to have more than one channel open at any given time for redundancy's sake. And we imagine open and close will probably be automated for the most part. In fact we already have a feature in LND called autopilot that can automatically open channels for a user. Frequency will depend whether the funds are needed on-chain or more useful on LN. -- Source
Will the lightning network reduce BTC Liquidity due to "locking-up" funds in channels?
When setting up a Lightning Network Node are fees set for the entire node, or each channel when opened?
You don't really set up a "node" in the sense that anyone with more than one channel can automatically be a node and route payments. Fees on LN can be set by the node, and can change dynamically on the network. -- Source
Can Lightning routing fees be changed dynamically, without closing channels?
Yes but it has to be implemented in the Lightning software being used. -- Source
How can you make sure that there will be routes with large enough balances to handle transactions?
You won't have to do anything. With autopilot enabled, it'll automatically open and close channels based on the availability of the network. -- Source
How does the Lightning Network stop flooding nodes (DDoS) with micro transactions? Is this even an issue?
I figured it was time to see for myself just how easy or difficult it was to use LN, and no better opportunity than to troll satoshis.place with some memes. I figured if there was a light wallet (Eclair) for android, there'd be something similar for Windows or even Linux to patch through Electrum. Well, after some research, there isn't, at least that I can find. If you want to use LN on desktop, you need a full client which means you need a full Bitcoin Core node. And apparently, if you want LN to work somewhat decently at all, you need a full client, because out of 100 or more tries to push to satoshis.place payment requests on Eclair for android, only a handful succeeded, as connection to the channel is constantly dropping off an on multiple times a minute, even with a channel opened directly to them. So I thought I'd try the other mobile LN wallet "Bitcoin Lightning Wallet". After funding it and opening a channel with a large hub, I thought I'd be able to route straight to satoshis.place. Unfortunately no, it appears you have to open a channel directly with who you want to transact with on this one as well, and it won't even let me open a channel with SP because "Data loss protection is not provided by this peer". Needless to say, it's pretty ridiculous in order just to have some fun on this stupid website, I'd have to spin up a Linux box, install a full Bitcoin Core wallet (yay, let me sync for a few days), then install a full LN Daemon on top if it which I'll need to keep online for as long as I have a channel open. The user experience is no where near at the point of SPV Bitcoin wallets, it barely works at all on the "easy methods".
Storage space: I am using an 8 GB microSD card for the OS, and a 128 GB USB drive for data. Minimums I would recommend: 8GB SD card and 32 GB USB drive.
Reddcoin Core client version: v22.214.171.124-a8767ba-beta (most recent version at this moment). ↳ Screenshot
You need the OS; Lubuntu. Download Lubuntu (707 MB) for the Raspberry Pi: https://ubuntu-pi-flavour-maker.org/download/. It's a .torrent download, so you will need a BitTorrent client. Message me or post in this thread if you need help with this.
You need software to write the OS to the SD card. I use Etcher. Download Etcher: https://etcher.io/.
Select image: select the lubuntu-16.04.2-desktop-armhf-raspberry-pi.img.xz file.
Select drive: select your microSD card.
Plug the SD card into your Raspberry Pi and power it up.
Lubuntu should boot up.
Set up Lubuntu, connect to the internet (wired or wireless). ↳ As username, I chose "rpi3b". You will see this username throughout this whole tutorial.
Make sure date and time are correct ([Menu] > System Tools > Time and Date). ↳ Click on Unlock to make changes. I personally change Configuration to "Keep synchronized with Internet servers". ↳ Screenshot
Reboot ([Menu] > Logout > Reboot). I am connected to wifi, but have issues getting wifi to work on initial boot. A reboot solves this issue.
Make sure system is up-to-date, install never versions.
Open LXTerminal ([Menu] > System Tools > LXTerminal). ↳ Screenshot
Enter the following in LXTerminal: sudo apt update && sudo apt upgrade ↳ Screenshot
You will be asked if you really want to continue. Enter Y (yes).
Updates are being installed! Wait until it's finished.
Install programs that will be used in this tutorial.
GParted: to partition the USB drive.
Htop: to see the amount of memory (RAM) and swap that is in use.
Enter the following in LXTerminal to install these 2 programs. sudo apt install gparted && sudo apt install htop ↳ Screenshot
Create 2 partitions on the USB drive: 1) Swap partition 2) data partition (for the Reddcoin blockchain) The swap partition is necessary: The Reddcoin wallet can be memory intensive. To prevent any crashes or freezes, add 2 GB of 'virtual' memory by creating a swap partition.
Important: Backup your USB drive if needed. The USB drive will be formatted, so the data on the USB drive will be wiped.
Please use the USB drive solely for this purpose, do not combine it with other stuff.
Keep your USB drive plugged in, do not (randomly) plug it out.
Plug your USB drive in.
GParted will be used to create the partititons. Start GParted via LXTerminal: sudo gparted ↳ Screenshot
Apply the changes. Click on the check mark or select Edit > Apply All Operations. ↳ Screenshot ↳ Screenshot
Important: The name of the swap partition is needed later, so please write it down. Mine is /dev/sda1 (first partition on first drive (drive 'a')). ↳ Screenshot
Reboot. After the reboot, the data partition you just created should be visible on your desktop. ↳ Screenshot
The swap partition is created, so now we can enable and use it.
The swap in use can be monitored with the program Htop. Open Htop ([Menu] > System Tools > Htop) to see the 'Swp' (swap) in use. ↳ Screenshot By default, swap is not used, so 0K. ↳ Screenshot You can leave Htop open.
To enable the swap partition, open LXTerminal and enter the following commands: (Assuming /dev/sda1 is your swap partition.)
Unpack the file (large file, takes around 15 minutes to unpack): sudo xz -d bootstrap.dat.xz ↳ Screenshot
After a successful unpack, your will find the file bootstrap.dat in your USB root folder. ↳ Screenshot
On the first run of the Reddcoin Core client, it will ask for a data directory to store the blockchain and wallet data.
Start the Reddcoin Core client: sudo /media/rpi3b/usb/reddcoin/src/qt/reddcoin-qt ↳ Screenshot
The welcome screen will appear and ask you about the data directory. I suggest a new folder on your USB drive, I picked blockchain. The directory will be created with all the necessary files. ↳ Screenshot
Click on the three dots (...) on the right. ↳ Screenshot
Click on Create Folder at the upper right corner. Type and enter in the folder name. (In my case: blockchain.) Click on Open. ↳ Screenshot ↳ Screenshot ↳ Screenshot
After selecting the directory, the Reddcoin Core client will start. Wait till it's fully loaded and close it.
Move the bootstrap.dat file to your data directory you selected in the previous step. By doing this, Reddcoin Core will use the bootstrap.dat file to import the blockchain, which speeds up syncing. sudo mv bootstrap.dat /media/rpi3b/usb/blockchain/ (Assuming blockchain as data directory.) ↳ Screenshot
The Reddcoin Core client set up is completed, but you still have to sync fully with the blockchain before you can send, receive and stake.
Keep the client running until it's fully synchronized. It will use the bootstrap file first, and download the rest of the blockchain to complete the sync. This can take some time (it took 2 days for me). Syncing the blockchain uses a lot of resources, so the software may react slow.
You can see the progress in the debug window (Help > Debug window). ↳ Screenshot
When the synchronization is completed, the red (out of sync) will disappear on the Overview screen! ↳ Screenshot
When synchronization is complete, you can start staking your Reddcoins.
You can write down your private key or copy and save it in a document. Make sure you save it somewhere only you can access it.
To import later: Debug window -> Console -> importprivkey [label] [label] is optional. ↳ Screenshot (without a label) ↳ Screenshot (with a label)
Boot with only 1 USB drive plugged in: Make sure only the USB drive (with the swap partition and data partition) is plugged in when you boot up your Raspberry Pi. This to make sure the swap partition (/dev/sda1) is recognized correctly. If you boot up with multiple USB drives, Lubuntu might see the USB drive with the swap partition as the second drive (instead of the first drive), and ignore the 2 GB swap partition. If this happens, starting Reddcoin can render the Raspberry Pi unresponsive.
Start Reddcoin Core easier Run a shell script (.sh file), so you can start Reddcoin just by double clicking on an icon on your Desktop.
Right Click on your Desktop and select Create New -> Empty File. ↳ Screenshot
Enter a file name, make sure it ends with .sh, and click on OK. I've chosen for Reddcoin.sh. ↳ Screenshot The file will be created on your Desktop. ↳ Screenshot
Add the command to start Reddcoin to the file.
Right click on the file, select Leafpad (to open the file in a text editor). ↳ Screenshot
Add the following to the file and save the file: sudo /media/rpi3b/usb/reddcoin/src/qt/reddcoin-qt ↳ Screenshot
To be able to execute the shell script (.sh), it has to have 'execute permissions'.
Right click on the file, and select Properties. ↳ Screenshot
Click on the Permissions tab.
For Execute, select Anyone, and click on OK. ↳ Screenshot
To start Reddcoin Core, double click on the file. A new window will pop-up, asking you what you want. Execute in Terminal is what we want, so you can click on enter. ↳ Screenshot Reddcoin Core will now start. Do not close the Terminal window, you can minimize it if needed.
Minimization options Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
Activate 'Minimize on close'. Settings -> Options... -> Window (tab) -> Minimize on close. ↳ Screenshot Reddcoin will still run when you click on the X button. To close/exit Reddcoin, right click on the Reddcoin icon in the system tray (bottom right corner). ↳ Screenshot
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
After your download is finished, open the file and click Install Package. ↳ Screenshot
To run the VNC Connect once:
Open [Menu] > Run, and enter: vncserver-x11 ↳ Screenshot
To auto run on startup:
Open Default applications for LXSession ([Menu] > Preferences > Default applications for LXSession). ↳ Screenshot
In LXSessions configuration, select Autostart in the menu left.
Under Manual autostarted applications, enter vncserver-x11 and click on + Add. ↳ Screenshot ↳ Screenshot
Reboot your Raspberry Pi and check if VNC Connect is started automatically after the reboot.
When VNC Connect is running, you'll see a VNC icon on the right bottom corner. Double click the icon to open VNC Connect and to see the IP address you need to enter to connect to your Raspberry Pi. ↳ Screenshot
(Upvote to the top) > SOLUTION FOR ZCLASSIC Eleos Wallet: "Wallet daemon can not be run. Check if daemon does not already run"
So I noticed a lot of people recently (including myself) are experiencing the error "Wallet daemon can not be run. Check if daemon does not already run" when trying to open up their ZCL Eleos wallet, and people are unable to access their funds or cannot export their private keys as well. A solution to this is now official (thanks to JBrutWhat from the BTCP team for helping me out on this.) Note: Post is being edited as more info becomes available to me. This solution also works for users who are on the ZClassic Swing wallet experiencing the error "A general unexpected critical error has occurred: error: Couldn't connect to server, see the console output for more detailed error information!." Eleos Wallet Troubleshooting section
The Wallet.dat file from the Eleos wallet or Swing wallet DOES NOT work with Zclassic electrum, so we are going to import the private key of the wallet into electrum instead.
Navigate to the c:\users\username\appdata\roaming\zclassic folder and copy the wallet.dat file from there, back it up somewhere.
Paste the wallet.dat you backed up earlier into the same folder as the walletaid tool folder
Right click the config.ini file and edit the file using notepad or notepad++ or your own text editor
remove the "#" symbol from the zclassic sections under "#Pubkeyprefix list" and "#privkeyprefix list"
copy the text "1cb8" and replace the "00" under the pubkeyprefix section under "[settings]" at the top
Doubleclick the walletaid.py file and press enter. Let it create the entire file with ALL the wallet addresses from your wallet.dat file. Or you could paste in the exact address you want and it should export a foundkeys.txt file into the walletaid directory. (The extract keys.bat file doesn't always work. It didn't work for me.) NOTE: If the walletaid.py script opens and instantly closes, this is because your wallet.dat file has a different name. Please rename your wallet file back to "wallet.dat" for compatibility.
Open up the foundkeys.txt file and it should list out every detected address and it's corresponding private key from your wallet.dat file you pasted in earlier
Do a ctrl + F and paste in the wallet address that contains your funds.
Locate the wallet address you are looking for and it's corresponding private key. We'll come back to this later.
IMPORTANT: MAKE SURE YOU DELETE THE PRIVATE KEYS FILE FROM YOUR COMPUTER AFTER FINISHING WITH IT. BACK IT UP TO AN OFFLINE USB STICK. DO NOT KEEP IT ON YOUR DESKTOP/HARD DRIVES OR ONLINE. Your private keys can potentially compromise ALL of your funds. Keep this safe and NEVER share it with anybody.
For users that are experiencing problems syncing their Electrum ZCL wallets, or their transactions are showing "not verified" after importing a wallet, this is because the blockchain_headers have not been successfully downloaded. We'll have to delete them let it re-sync. For Windows users, first close the electrum wallet. Then navigate to C:\Users\UsernameXXX\Appdata\Roaming\Electrum-ZCL\ and from there delete ONLY the "blockchain_headers" file. Then re-open the wallet and allow it to sync. For Mac OS users, close the wallet and navigate to ~/.electrum-zcl/ and delete ONLY the blockchain_headers file once again. Then reopen the wallet. Please see github issue #77 thread here for more help.
Create a new standard wallet and restore the 2FA wallet using your "seed" codes. DO NOT password protect this wallet.
Disable the 2FA feature when presented with the option.
Navigate to C:/Users/YOUR-NAME/AppData/Roaming/Electrum-zcl/wallets. Open the new standard wallet file with Notepad.
You will need to gather the 2 private keys and one public key. To find this easily, press “CTRL+F” and search for “xprv”. Copy the 2 “xprv” values as well as the last “xpub” value. You will need these in a later step.
Create a new “Multi-signature wallet”. Select “From 3 co-signers” on the first slider. Select “Require 2 signatures” on the second slider.
To add the first co-signer, click “Use public or private keys”. Enter the first xprv key in this box.
Add the second co-signer via a private key also.
Add the third co-signer with the public key. Complete the set-up.
Your wallet funds now have the ability to be sent from the multi-signature wallet.
It's recommended by the BTCP team to switch over to the ZCLASSIC Electrum wallet ASAP as the Eleos wallet has become unstable now. The original ZClassic swing wallet is reported to still be working. Up to you whether or not to use the electrum wallet, but I'd personally recommend it.
Open up the wallet and create a new wallet, then when it gives you the option to import private keys, paste in your appropriate private key from the foundkeys.txt file we generated earlier.
Afterwards, your wallet should have successfully migrated your wallet into the ZCL electrum wallet. There's currently a synchronization issue upon first boot of the wallet, so close and re-open it again and you should be fine. If not, try closing the electrum wallet, navigate to "c:\users\username\appdata\roaming\Electrum-zcl folder and delete the "blockchain_headers file, as initial download of the blockchain headers sometimes initially fails. Then restart the wallet and you should be fine, according to the dev team.
Users of older ZCL electrum wallets before version 1.0.3 should download the latest version. I was on the older version (1.0.0 and noticed my wallet wouldn't sync.) So I upgraded to the latest version and wallet has successfully synced.
Also make sure to encrypt your electrum wallet by clicking the little settings icon at the bottom right.
For Users who were already using the Electrum wallet beforehand, you can go to file > new/restore wallet > next > import zclassic private keys and input the private key you obtained from the walletaid tool, and it should import the wallet into the electrum wallet. Then from there, go to file > backup wallet and export a copy of the wallet.dat file onto an offline USB.
Side notes: ZCL-Electrum wallet Does support mining directly to it. More ZCL Electrum servers will be added along with newer releases soon. Another note: Every time you want to migrate funds from one address to another, test it with a small amount first before proceeding with the full amount. BTCP Team has also partnered with Coinomi to release a wallet supporting ZCL and BTCP after the hard fork occurs.
Reminder: Backup and delete the private keys file from your desktop pc/hard drive, move it into an offline USB for safekeeping. Do not leave it on an online device. Donate to me if you found the guide useful! Your donations 100% voluntary but they are greatly appreciated and keep us going! ZCL: t1fkxCWJs3f2oXznGwZuEgftJ2SCjYZ8VjZ BTC: 14Xmfm9jf4h1h4RXZBQCFK6i4LWibqWVPu LTC: LhAERgWcjbbXQbGqjhy4owALGhwfpj1aw2 ETH: 0xe723305337926e1fcb5dd0495e6648569a252c13 BCH: 1JXqLHqjYH8bew38AXwEt9dmKvsdYwLtvr LINKS (You can join the discord rooms where there are channels for users looking for help)
Getting frustrated with Ubuntu. Are my experiences the norm for a Linux user?
Let me start off by saying that I'm not a total newb, but still pretty green. I like to believe I'm capable with computers, and know enough to figure out most issues. I also have a pretty solid general understanding of how they function. Been a Windows user most of my life, but decided to make the switch to Linux a few years back. My experiences thus far are making me reconsider the switch, despite the fact that I've really become opposed to using Windows. I'm curious if I should expect more of the same indefinitely, or if my experiences up to this point are unusual, and I should expect to reach a point where I can just use the OS, instead of spend hours trying to perform every task. It all started when I downloaded Ubuntu about three years ago. I easily got it installed as a dual boot on a Windows machine. Had to start by allocating disk space in Windows for the new Linux install, prepared a live usb, went through the install, cake. Then I started trying to do stuff, like use a printer. Well HP doesn't make a driver for Linux and, probably, 2-4 hours of research led to me still not having a working printer. I found a driver, but the process to get it installed did not work as it was supposed to. I forget the specifics, but I followed a tutorial to the T, but ran into unforeseen installation issues, and never could figure out how to get the process complete. After that I started running into issues with the FireFox browser. I've alwasy used FF on Windows with no issues. On Ubuntu it ran slower than dial-up from the mid-90's. Again, 2-4 hours worth of research and several changes to things like FF settings, disabling add-ons, etc., and I still had no fix. Still I wasn't deterred. Then the dual boot broke. I tried boot repair. No dice. Tried for several hours to get it working. Asked about it on forums, sent in results of boot repair (where I forget) only to get no response, and finally I threw in the towel. I also struggled to get Bitcoin Armory working, with some very frustrating success, but I didn't count that against Linux, since it was very new software, and I wasn't surprised it was buggy. Fast forward to today. I've been using Windows for a couple years, with few attempts made to use Linux, except for trying to retrieve a very small amount of BTC from Armory, which consumed about three weekends of my life to finally achieve. Now I've decided to give it another go. I downloaded UbuntuStudio b/c I'd like to use some of the music production software that comes with it. Following some tutorials online, I tried to connect my midi keyboard to the computer using QJackCtl. I couldn't remember the issue that I ran into when starting to type this up, so I tried to repeat the process, only to have the program crash during start up, three times. The computer had literally just restarted 20 minutes ago, so I doubt a reboot would work, but maybe. It's almost funny at this point. I'm really disappointed that I can't get the audio software that came with the distro working "fresh out of the box." Maybe with a few hours, or weekends, worth of research? I've also been getting a system error message every time I login. I posted a query on the Ubuntu forums. That issue has yet to be sorted out. I hesitate to include this next part, because it involves software that is really still in it's early stages, and I'm trying to be realistic in taking the perspective that any problems I encounter are with the new software, not Ubuntu, but the fact that I had zero problems getting the same stuff to work in Windows just adds to my frustration with Ubuntu. Everything I'm about to describe is involved with installing monero mining and wallet software. The exception is the AMD drivers needed for the GPU I'm using to mine. Those I expected to work without issue. I followed the directions for installing the AMD drivers for Ubuntu on the AMD website, and the program would not work. After, you guessed it, 2-4 hours of research, I finally, almost by accident, installed an older version of the driver software. Boom, it worked. WTF man?! When I installed the Windows version it took 2 minutes. Moving on, I tried getting the xmr-stak mining software working. This took me several hours, spread over several days to sort out. Same with the monero-gui wallet, which actually I've only got half-way working. In fact, I've tried installing the monero-gui by two different ways. In the process I've inadvertently got the monerod daemon running, but not the gui. Actually, the monerod daemon starts with the computer and I haven't even started trying to figure out how to turn that off, since what's the point of having it run if I can't use the gui? In Windows I had all of this up and running in a couple of hours. And in saying that I'm prepared for the "if you like Windows so much then use that!" or "you're just too thick to figure it out!", but I don't like Windows, and I don't think it's a matter of not figuring it out. It seems to me that the reason I've spent dozens of hours just trying to get things to work in Linux is that nearly every time I've tried to do something, there is inevatably some error along the way where following the directions isn't good enough, and sorting out the issue is a feat in and of itself. I just want to know if this is unusual, or if this is how it's going to go forever if I keep using Linux. Is my experience typical? TL;DR: I've had a litany of issues and spent countless hours trying to fix them using Linux. Is this rare, and I've just had an unusual experience, or actually pretty common, and I should just accept it as the cost of using an open source OS?
The Bitcoin Core daemon (bitcoind) is not included in the .dmg file you may have downloaded to install Bitcoin-QT. Bitcoind, along with its support binaries, is instead included in the OS X .tar.gz file listed on the official Bitcoin Core download page. ... Windows 7 & 8: Press Win-R (Windows key plus the R key) to open the Run dialog. Type cmd ... When running bitcoind from a systemd service, as in Bitcoin Core daemon running on a Windows 7 seems to be not supported with the following error: Exchange Coinrail confirmed that it had Ishares Etf Pir been hacked. The November CME contracts, which allows traders to profit from declines in BTC, will expire Friday afternoon. The first step is finding the default data directory. Mac, Windows, and Linux version of Bitcoin Core each store data in a different location. The procedure described here will use a graphical file browser to find it. On Windows 7, begin by clicking on the Windows menu. Then click your username from the right-hand menu. bitcoind is a program that implements the Bitcoin protocol for remote procedure call (RPC) use. It is also the second Bitcoin client in the network's history. It is available under the MIT license in 32-bit and 64-bit versions for Windows, GNU/Linux-based OSes, and Mac OS X. . As part of Bitcoin Core, bitcoind has been bundled with the original client from version 0.2.6 to 0.4.9, and with ... Bitcoin Core Daemon. If you can provide instructions and screenshots for running the latest version of Bitcoin Core daemon on Windows 7, please open an issue and we’ll tell you what we need. The instructions for Windows 8.x may already provide all the necessary information. Mac OS X Instructions
Suscribete : http://goo.gl/0bmaeq Link de descarga : http://sh.st/sYYoK Hola Amigo Y Amiga ! Bueno como ya han observado en el titulo hoy te traigo como desc... ¡Bienvenido! │ Clic en mostrar más. Hola amigos en este nuevo vídeo les traigo un magnifico programa para montar imágenes ISO pro y full bueno dicho eso si t... ¡Bienvenido! │ Clic en mostrar más. En este vídeo te mostrare como descargar e instalar Daemon Tools Lite para Windows 7, 8 y 10. — — — — — ENLACE │ LINK — —... link para download: http://adf.ly/1iBh6F canla vale tudo https://www.youtube.com/channel/UCeblwaPv0eTwnTQTaDfz11w pagina oficial vale tudo https://www.facebo... O Daemon Tools é um excelente programa para emuladores, sendo muito utilizado para baixar grandes arquivos em imagem no formato .ISO. Com ele você ira montar...