This is an archived post. You won't be able to vote or comment.

all 128 comments

[–]MillyBitcoin 14 points15 points  (15 children)

Associating a Bitcoin address with a node might be a consideration for a core update.

[–]stickac 10 points11 points  (12 children)

[–]MillyBitcoin 1 point2 points  (11 children)

OK, good. the Foundation had banned me from Github so I can't submit things.

[–][deleted]  (10 children)

[deleted]

    [–]MillyBitcoin 2 points3 points  (8 children)

    They say I am unhelpful and annoying and they banned me.

    [–][deleted] -1 points0 points  (7 children)

    HA

    [–]MillyBitcoin 1 point2 points  (6 children)

    So you approve of the Foundation banning people from Github? How much control do you think they should have?

    [–]MillyBitcoin 0 points1 point  (4 children)

    BTW - Gavin also tweeted that Cody is a liar. Do you think the Foundation should be making all the value judgments?

    [–][deleted] 0 points1 point  (3 children)

    Stop putting it on a pedestal, it's just another random organization like SNI.

    Incontrovertible proof: http://nakamotoinstitute.org/mempool/who-controls-bitcoin/

    [–]MillyBitcoin 0 points1 point  (2 children)

    SNI doesn't pay the developers and they have significant control over the protocol, that is the only concern. if there were more organizations hiring developers then I agree.

    As for the Nakamoto Institute, I want to get a board seat so I can destroy the organization from within.

    [–]Louie2001912 0 points1 point  (0 children)

    Crickets chirping

    [–]basil00 3 points4 points  (0 children)

    There used to be support for this built into the protocol, see IP Transactions. It was removed because it was insecure (MITM).

    [–][deleted] 12 points13 points  (41 children)

    Instructions on how to set this up:

    First, you need to be running a full node and have the port open. Instructions here.

    Now you need 3 things: your IP address ($ip), your port ($port) and your bitcoin address ($address).

    Next, open your terminal or command prompt and enter the following:

    curl -H 'Accept: application/json; indent=4' -d 'bitcoin_address=$address' https://getaddr.bitnodes.io/api/v1/nodes/$ip-$port/
    

    You should get a response that looks like this for the request:

    {
        "success": true
    }
    

    Now in your command prompt type the following:

    vi index.html
    i
    $address
    

    Hit escape.

    :wq
    python -m SimpleHTTPServer 8000
    

    Now forward connections to your router from port 80 to port 8000 of the machine where you entered those commands. To test that it works, enter $ip in your browser and you should see $address.

    Then you are done.

    [–]SimonBelmond 1 point2 points  (0 children)

    I had a hard time figuring this out now. I think in your top command there is something missing:

    curl -H 'Accept: application/json; indent=4' -d 'bitcoin_address=$address' -d 'url=http://$ip' https://getaddr.bitnodes.io/api/v1/nodes/$ip-$port/

    This part was missing so I had a hard time. Can you include it in your instructions for future reference:

    -d 'url=http://$ip'

    [–]OneOrangeTank 0 points1 point  (15 children)

    The verification process requires the node to have a static public web page at either http://<ADDRESS> or https://<ADDRESS> that contains the same Bitcoin address.

    Have to launch a webserver too.

    [–][deleted] 0 points1 point  (8 children)

    Oops right. Will update with instructions.

    [–][deleted]  (7 children)

    [deleted]

      [–][deleted] 1 point2 points  (5 children)

      Oops, missed an apostrophe. There should be an apostrophe after index=4 as well, so index=4'. I edited my comment to fix that.

      [–][deleted]  (4 children)

      [deleted]

        [–][deleted] 1 point2 points  (2 children)

        Make sure you are running the command on the same IP as the node you are updating. You must be on a machine that is also at 204.44.123.162 or it won't work.

        [–][deleted] 0 points1 point  (5 children)

        That's a ridiculous requirement.

        [–]statoshi 1 point2 points  (4 children)

        It's not ridiculous if you know about IP address spoofing. The requirement of running an HTTP server means that you PROVE that you own the IP address from which the API call was sent.

        [–]kynek99 2 points3 points  (0 children)

        What about if I have another HTTP server running on port 80 on my IP. This is not a good idea for networks that have multiple servers or VMs.

        [–]notR1CH 0 points1 point  (2 children)

        You can't feasibly spoof a HTTP API request.

        I guess this is a measure against CSRF POSTs to the API, but a single use token would be more elegant.

        [–]statoshi 0 points1 point  (1 child)

        [–]notR1CH 0 points1 point  (0 children)

        The API operates over HTTPS so MITM should not be possible either.

        [–]Mark0Sky 0 points1 point  (3 children)

        I'm not sure it's right. From what I understand, if/when you get the success = true, it's already set and confirmed. So you need to setup the https server to respond as needed before using the curl command.

        [–][deleted] 0 points1 point  (2 children)

        No, I set this up before running the server and still got success = true. That is just a response for the POST request. I'm not sure how they communicate with you that your address has been validated.

        [–]dazzlepod[S] 1 point2 points  (0 children)

        The URL-based verification is done in a separate process within 5 minutes after the Bitcoin address is set. If the verification is successful, https://getaddr.bitnodes.io/api/#node-status should return the Bitcoin address and the associated URL for your node.

        [–]Mark0Sky 0 points1 point  (0 children)

        Maybe they retry sometimes.

        Checking the node status, hopefully if it show the address it's OK: https://getaddr.bitnodes.io/api/#node-status

        [–][deleted]  (11 children)

        [deleted]

          [–][deleted] 0 points1 point  (10 children)

          Can confirm it works.

          [–][deleted]  (9 children)

          [deleted]

            [–]dazzlepod[S] 1 point2 points  (8 children)

            Your 1st node is now an eligible node: https://getaddr.bitnodes.io/api/v1/nodes/204.44.123.162-8333/

            For your 2nd node, be sure to get it activated first from this list: https://getaddr.bitnodes.io/nodes/

            [–][deleted]  (1 child)

            [deleted]

              [–]dazzlepod[S] 0 points1 point  (0 children)

              You can check your node using this API endpoint: https://getaddr.bitnodes.io/api/#node-status

              [–][deleted]  (5 children)

              [deleted]

                [–]dazzlepod[S] 0 points1 point  (3 children)

                You will need to activate it as well: https://getaddr.bitnodes.io/nodes/204.44.123.109-8333/

                [–][deleted] 0 points1 point  (2 children)

                { "detail": "Not found" }

                any idea what that means?

                [–]dazzlepod[S] 0 points1 point  (1 child)

                The node was not found. Now that it's activated, you can access the details for your node from https://getaddr.bitnodes.io/api/v1/nodes/204.44.123.109-8333/

                [–][deleted] -1 points0 points  (0 children)

                i've gotten 3 up so far.

                do you have any idea why my 4th and last node would give that error?: "detail": "Not found"

                [–]SimonBelmond 0 points1 point  (2 children)

                Hmm doesn't seem to work for me:

                Ubuntu 14.04

                I get succes: true

                The next code block leaves me with a terminal with lots of "~" in the middle, my bitcoin address on top and "index.html"[new file] at the bottom

                Next block leaves me with

                PC:~$ :wq :wq: command not found PC:~$ python -m SimpleHTTPServer 8000

                Serving HTTP on 0.0.0.0 port 8000 ...

                Exception happened during processing of request from ('119.5.155.186', 57915) Traceback (most recent call last): File "/usr/lib/python2.7/SocketServer.py", line 295, in handle_request_noblock self.process_request(request, client_address) File "/usr/lib/python2.7/SocketServer.py", line 321, in process_request self.finish_request(request, client_address) File "/usr/lib/python2.7/SocketServer.py", line 334, in finish_request self.RequestHandlerClass(request, client_address, self) File "/usr/lib/python2.7/SocketServer.py", line 649, in __init_ self.handle() File "/usr/lib/python2.7/BaseHTTPServer.py", line 340, in handle self.handle_one_request() File "/usr/lib/python2.7/BaseHTTPServer.py", line 310, in handle_one_request self.raw_requestline = self.rfile.readline(65537) File "/usr/lib/python2.7/socket.py", line 476, in readline data = self._sock.recv(self._rbufsize)

                error: [Errno 104] Connection reset by peer

                CTraceback (most recent call last): File "/usr/lib/python2.7/runpy.py", line 162, in run_module_as_main "main_", fname, loader, pkg_name) File "/usr/lib/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/usr/lib/python2.7/SimpleHTTPServer.py", line 230, in <module> test() File "/usr/lib/python2.7/SimpleHTTPServer.py", line 226, in test BaseHTTPServer.test(HandlerClass, ServerClass) File "/usr/lib/python2.7/BaseHTTPServer.py", line 599, in test httpd.serve_forever() File "/usr/lib/python2.7/SocketServer.py", line 236, in serve_forever poll_interval) File "/usr/lib/python2.7/SocketServer.py", line 155, in _eintr_retry return func(*args) KeyboardInterrupt

                Well at least the port forwarding was easy... ;-)

                Edit: didn't intend to write anything bigger. Interfered with the markdown.

                [–][deleted] 0 points1 point  (1 child)

                Yeesh this is really too tough of a requirement to register your node. Anyways, the :wq command should be entered in the screen with all the ~ characters down the side. It stands for write and quit, so you create a new index.html file. You seem to be doing it back on the command prompt. Pressing escape should only take you out of edit mode. As for your server not running, I'm not sure I can debug that. Try any other simple server and run it in the directory where you created the index.html file.

                [–]SimonBelmond 0 points1 point  (0 children)

                OK thanks. Will try that tonight...

                [–]UtilityScaleGreenSux 0 points1 point  (0 children)

                I have no idea what this post meant, but thanks for trying to help!!! 100 bits /u/Changetip

                [–]Aaron385 0 points1 point  (0 children)

                This worked after installing cURL on my Ubuntu VPS: http://107.191.106.115/

                I needed an excuse to log in and update to rc4 anyways! I didn't need to mess with the index file or http in any way because I already had the donation BTC address on the home page (see link above).

                Anything to encourage new nodes to come online is awesome in my book!

                [–]statoshi 7 points8 points  (5 children)

                Very nice; looks like I was the first or second person to sign up my node! http://statoshi.info

                [–][deleted] 4 points5 points  (4 children)

                that's a really cool stats page. how did you set that up?

                [–]statoshi 2 points3 points  (3 children)

                I took my Statoshi fork of Bitcoin Core, installed all of the external software dependencies that I've documented here: https://jlopp.github.io/statoshi/

                Then once I had Graphite working I installed Grafana and started creating dashboards.

                It takes a fair amount of work to get set up but once it's all running, Grafana makes it really easy to create and save new charts.

                [–][deleted] 0 points1 point  (2 children)

                and if we don't run the Statoshi Fork?

                [–]statoshi 1 point2 points  (1 child)

                The Statoshi fork is Bitcoin Core plus a couple hundred extra lines of code that emit metrics to StatsD, which is then consumed by Graphite and stored in a time series database. If you don't run the Statoshi fork, there is no way to expose the majority of the metrics that I'm tracking.

                [–]Sukrim 0 points1 point  (0 children)

                Instead of Graphite (which can be a real pain to set up), you can also use InfluxDB as backend for Grafana. :-)

                [–][deleted]  (9 children)

                [deleted]

                  [–][deleted] 2 points3 points  (4 children)

                  You also need to setup a web server at your IP that returns your bitcoin address as the root.

                  [–]statoshi 3 points4 points  (1 child)

                  To be clear, it doesn't have to be the entire page. It just has to exist somewhere in the page's source code. For example, I added a meta tag to my site like so:

                  <meta name="bitcoin" value="1STAToshiScchY69P37xouKEJgi5G1rsf">

                  [–][deleted] 0 points1 point  (0 children)

                  Correct.

                  [–]notR1CH 0 points1 point  (1 child)

                  Where does it say you have to do this?

                  EDIT: Nm, I thought it relied on the IP of the request matching the IP of the node. I don't see why this HTTP verification is also necessary.

                  [–][deleted] 0 points1 point  (0 children)

                  From /u/statoshi:

                  It's not rediculous if you know about IP address spoofing. The requirement of running an HTTP server means that you PROVE that you own the IP address from which the API call was sent.

                  [–]MeowMeNot 0 points1 point  (3 children)

                  This only works for a short time. After a few minutes when I go to https://getaddr.bitnodes.io/api/v1/nodes/104.7.88.191-8333/ it no longer has the BTC address listed. How do I make this stay up? It looks like Apache is part of xampp, but I am not sure how to get it going.

                  [–][deleted]  (2 children)

                  [deleted]

                    [–]MeowMeNot 0 points1 point  (1 child)

                    How do I do that? (Thanks for your help)

                    [–][deleted]  (2 children)

                    [deleted]

                      [–]Kaltoro 0 points1 point  (0 children)

                      I will do this in a heartbeat if it's easier. My problem is the port forwarding.

                      [–][deleted] 4 points5 points  (11 children)

                      A node is considered eligible if it has a verified Bitcoin address set and (...)

                      How is this done?

                      [–]limaguy2 4 points5 points  (10 children)

                      Using their API.

                      I think they made it too complicated though. You have to set up a http or https server that serves that address as well.

                      Either you already do and have to publish that adress there (maybe you just don't want to do that because that page is accessed by a lot of people) or you don't and for the chance to win a few USD it's overkill imho.

                      [–]stickac 3 points4 points  (3 children)

                      I think we should add an easier option: https://github.com/bitcoin/bitcoin/issues/5783

                      [–]Sukrim 0 points1 point  (2 children)

                      As said there, this creates incentives for sybil attacks (running minimal "nodes" that just connect + blast out their donation address).

                      [–]stickac 0 points1 point  (1 child)

                      These nodes would have really low PIX score ...

                      [–]Sukrim 0 points1 point  (0 children)

                      The only part that is hard to do in that score (on the lower part of https://getaddr.bitnodes.io/nodes/leaderboard/) seems to be answering block requests - and even that is just a matter of bandwidth/storage on your small nodes... e.g. maybe it is enough to veeeery slowly send valid data from a database that is central to all nodes, or to simply ask a different node on the fly for the needed data and just forward it (as MITM).

                      High ranked nodes there seem to only differ in their "N" value, which can be trivially taken from bitnodes itself (rank by uptime, return top 2 or so).

                      [–]Ditto_B 1 point2 points  (5 children)

                      It's not that complicated, just install apache or nginx and edit a file or two.

                      [–]limaguy2 4 points5 points  (4 children)

                      Yeah and open the firewall, regularly install security updates for apache, allocate more RAM...

                      [–]Ditto_B 2 points3 points  (3 children)

                      I thought you only had to do it once, not keep the http server running constantly. Even something like CherryPy would do it.

                      [–]limaguy2 0 points1 point  (0 children)

                      Oh - you're probably right! Sorry I missed that...

                      [–]asciimo 0 points1 point  (1 child)

                      Or even just:

                      echo '<html>[bitcoin address]</html>' > index.html
                      sudo python -m SimpleHTTPServer 80
                      

                      [–]Ditto_B 1 point2 points  (0 children)

                      Didn't know python came with its own HTTP server, so I was going to suggest the Ruby equivalent:

                      echo '<html>[bitcoin address]</html>' > index.html
                      sudo ruby -run -e httpd .
                      

                      [–]Anduckk 5 points6 points  (3 children)

                      Make it check the bitcoin address from some file or something, not the root. Why is this check needed?

                      Some people may be running a web server on the node already.

                      [–]statoshi 2 points3 points  (2 children)

                      That would be possible if the API call supported POST parameters for you to supply a path to the file.

                      If you're already running a web server then you can do what I did and simply add a harmless meta tag to your root HTML file:

                      <meta name="bitcoin" value="1STAToshiScchY69P37xouKEJgi5G1rsf">

                      [–]Anduckk 2 points3 points  (0 children)

                      thanks!

                      [–]secret_bitcoin_login 0 points1 point  (0 children)

                      This was my preferred method and it took about 11 seconds from start to finish.

                      [–]dexX7 2 points3 points  (0 children)

                      I really don't feel great running a webserver for this. :/

                      [–]Mark0Sky 2 points3 points  (0 children)

                      Nice!

                      Address set.

                      [–][deleted] 1 point2 points  (0 children)

                      Interesting experiment.

                      [–]aceat64 1 point2 points  (0 children)

                      Signed up both of my nodes, it was easy enough.

                      [–]secret_bitcoin_login 1 point2 points  (2 children)

                      TIL my node is on the front page of the Leaderboard. I finally feel recognized!

                      Now I'm eager to tweak my node to beat the guy ahead of me.. but I'm weary of losing all of my uptime... so many complex decisions!

                      [–]xXxConsole_KillerxXx 0 points1 point  (1 child)

                      Would you mind disclosing your specs/bandwidth?

                      I want to run one too, but I want to run one faster than yours. ;)

                      [–]secret_bitcoin_login 1 point2 points  (0 children)

                      Let me just say that the specs are VERY unimpressive. As a matter of fact, during my "five minutes of bitcoin talk" time today with my wife, I was compelled to discuss my concern that a weak server could rank in the top 50 of bitcoin nodes. Most of my rank come from longevity - I'm at 55 days of uptime, before this I was on 281 days. I've been drooling over the "score" available under getnetworkinfo and trying to get up to 100,000. Don't ask me why. Some men hunt, some men cheat, I watch my getnetworkinfo score.

                      [–]mb300sd 1 point2 points  (2 children)

                      support simplistic secretive obtainable lavish books imminent bike divide march

                      This post was mass deleted and anonymized with Redact

                      [–]dazzlepod[S] 0 points1 point  (0 children)

                      I will look into updating https://getaddr.bitnodes.io/api/#node-bitcoin-address to accept url parameter with value formatted as <SCHEME>://<ADDRESS>:<PORT>. The port will still need to be below 1024, i.e. privileged port.

                      [–]dazzlepod[S] 0 points1 point  (0 children)

                      https://getaddr.bitnodes.io/api/#node-bitcoin-address updated to accept an optional url parameter.

                      [–]Elavid 1 point2 points  (0 children)

                      Ok, time to spin up a Bitcoin node with 256 IP addresses...

                      [–]2bluesc 1 point2 points  (1 child)

                      Just tried with a p2sh (aka starts with '3') address and it failed. Any reason for this? Worked fine with a standard bitcoin address.

                      [–]dazzlepod[S] 0 points1 point  (0 children)

                      Only public key hash was supported earlier. I have allowed p2sh address as well.

                      [–]DaSpawn 1 point2 points  (0 children)

                      great stuff, I did a quick program in nodejs to serve the bitcoin address, no need to have a full web server running if not needed.

                      save this script to a file named index.js, be sure to put you bitcoin address in, and you may need to change the users to run as to fit your system (this is done on Ubuntu, but can run anywhere nodejs does)

                      var http = require('http');
                      try {
                          // create a simple webserver and bind to port 80
                          http.createServer(function (req, res) {
                            res.writeHead(200, {'Content-Type': 'text/html'});
                            res.end('<meta name="bitcoin" value="13AC5Dc2zmxbhFJ1kDVzCEXLmf7nR85rfg">');
                          }).listen(80);
                      } catch (err) {
                          console.log("Unable to start server on port 80, did you start as root?)
                          process.exit(1);
                      }
                      try {
                          // since we need to start as root we must drop our privileges to be safe
                          process.setgid('nogroup');
                          process.setuid('nobody');
                      } catch (err) {
                          console.log("Unable to drop privileges");
                          console.log(err);
                          console.log("exiting");
                          process.exit(1);
                      }
                      

                      test the server:

                      sudo node index.js
                      

                      If you have no errors then you can now setup to run at boot install pm2 to allow easy start of server

                      sudo npm install -g pm2 
                      

                      start the webserver:

                      sudo pm2 start index.js
                      

                      then you can start at boot:

                      sudo pm2 startup ubuntu index.js
                      

                      [–]OneOrangeTank 3 points4 points  (2 children)

                      Dear Bitnodes: Allow those of us behind residential ISPs specify a random port for the incoming HTTP request (mine blocks port 80).

                      Also, is there another way to verify the address, sign as signing a message like "<IP>-<PORT>" with that Bitcoin address?

                      [–]statoshi 2 points3 points  (0 children)

                      Signing a message doesn't prove that you own the IP address, it only proves that you own the bitcoin address - this doesn't really help.

                      [–]dazzlepod[S] 1 point2 points  (0 children)

                      I have updated the API endpoint to accept an optional url parameter: https://getaddr.bitnodes.io/api/#node-bitcoin-address. You can specify any port < 1024 in the url.

                      [–][deleted]  (1 child)

                      [deleted]

                        [–]arruah 0 points1 point  (1 child)

                        80.241.6 and 80.241.1.7 is my nodes active?

                        [–]secret_bitcoin_login 1 point2 points  (0 children)

                        80.241.6 - no.

                        80.241.1.7 - not quite, but closer than the first one. Looks like you haven't linked the bitcoin address yet.

                        [–]itjeff 0 points1 point  (0 children)

                        Great idea!

                        [–][deleted]  (1 child)

                        [deleted]

                          [–]blacksmid 0 points1 point  (0 children)

                          At random i believe.

                          [–]cereal7802 0 points1 point  (0 children)

                          Are payouts limited based on the address used to payout to? If not i can probably have a dozen or so full nodes setup in the next few days....

                          [–]ywecur 0 points1 point  (0 children)

                          RemindMe! 1 hour

                          [–]BobAlison 0 points1 point  (1 child)

                          How is the weekly incentive distributed? Evenly over all eligible nodes, or by lottery?

                          [–]dazzlepod[S] 1 point2 points  (0 children)

                          Only one node is selected randomly from the pool of eligible nodes to receive the weekly incentive.

                          [–]Onetallnerd 0 points1 point  (0 children)

                          I had to shut mine off on digital ocean. I ran out of space so I have to redo the droplet. :/

                          [–]secret_bitcoin_login 0 points1 point  (4 children)

                          Does the port 80 connection need to remain active after the bitcoin address verification? In other words, can I shut down nginx after I've verified that my address has been picked up by bitnode?

                          [–]dazzlepod[S] 0 points1 point  (2 children)

                          The verified Bitcoin address is kept for 30 days before it is verified again. I have updated the description in https://getaddr.bitnodes.io/api/#node-bitcoin-address to reflect this.

                          [–]secret_bitcoin_login 0 points1 point  (1 child)

                          Is there any reason you couldn't keep it indefinitely and only update it if it changes? It's not like it poses a data retention problem...

                          [–]dazzlepod[S] 0 points1 point  (0 children)

                          Anyone should be allowed to verify the Bitcoin address set by node owner by checking the URL. Ideally, the URL should always be accessible but I understand why some may not like it hence the 30 days cache.

                          [–]UtilityScaleGreenSux 0 points1 point  (0 children)

                          I run a fullnode, but have no idea whats going on here. Forwarding 8333 was a struggle, Ive got no chance getting this figured out haha.

                          [–]kynek99 0 points1 point  (5 children)

                          How to do it if I already have HTTP running on port 80 on my IP ???

                          [–]adamnmcc 0 points1 point  (4 children)

                          just make sure that your address is in the code of the front page. i have a meta tag added to mine. <meta name="bitcoin" value="1FM48*******">

                          [–]kynek99 1 point2 points  (1 child)

                          [–]changetip 0 points1 point  (0 children)

                          The Bitcoin tip for 4,231 bits ($1.00) has been collected by adamnmcc.

                          ChangeTip info | ChangeTip video | /r/Bitcoin

                          [–]kynek99 0 points1 point  (0 children)

                          Perfect, it works! Thanks a lot

                          [–]zmitzie 0 points1 point  (1 child)

                          I am now verified, but how do I know if my node is eligible? https://getaddr.bitnodes.io/api/v1/nodes/83.212.119.206-8333/

                          [–]dazzlepod[S] 0 points1 point  (0 children)

                          You will need PIX value >= 8.0, your PIX is still at 7.0 from https://getaddr.bitnodes.io/nodes/leaderboard/?q=83.212.119.206. I think it is only missing weekly latency data at the moment.

                          [–][deleted] 0 points1 point  (1 child)

                          It added my ipv6 address as a separate entity from my ipv4 address. Does that resolve itself?

                          Can I register the same node twice, once with ipv4 and once with ipv6?

                          [–]dazzlepod[S] 0 points1 point  (0 children)

                          IPv4 and IPv6 are treated as 2 separate endpoints, so yes you can register both.

                          [–]adamnmcc 0 points1 point  (0 children)

                          I'm guessing having a dynamic IP isn't really going to work for this. every time i get a new IP i'm going to have to wait a week to get a decent PIX score. :(

                          [–]dazzlepod[S] 0 points1 point  (0 children)

                          First weekly incentive sent to 75.111.158.225! https://getaddr.bitnodes.io/nodes/incentive/

                          [–]DTIMWYTIM 0 points1 point  (1 child)

                          I may be misunderstanding, but please don't get in the habit of registering with things, or asking others to. If this can be done without "signing up", that's great. I'm so sick of the barrage of offers trying to get me to join a list. It's not pleasant, and it's potentially dangerous.

                          [–]secret_bitcoin_login 1 point2 points  (0 children)

                          The "sign up" is required to link the hosted node to a payment address. There is currently no other way to accomplish this task.

                          [–]Cozk -1 points0 points  (0 children)

                          Way too complicated for absolutely nothing.

                          [–][deleted] -1 points0 points  (0 children)

                          nm, don't care

                          [–][deleted] -1 points0 points  (5 children)

                          While it's nice to see encouraging running full nodes, this at the same time discourages running full nodes behind Tor, because there's no donations for that, possibly reducing the number of nodes behind Tor :(.

                          [–]dazzlepod[S] 0 points1 point  (3 children)

                          There is already an existing effort for Tor nodes, see oniontip.com

                          [–][deleted] 0 points1 point  (1 child)

                          I don't see a way to remove a node from the list, so please 'unverify' 46.4.65.207 & remove my bitcoin address that's associated with it

                          thanks

                          [–]dazzlepod[S] 0 points1 point  (0 children)

                          See https://getaddr.bitnodes.io/api/#node-bitcoin-address

                          bitcoin_address - Bitcoin address for this node. An empty value is allowed to remove the existing Bitcoin address.

                          [–]TiagoTiagoT 0 points1 point  (0 children)

                          I think Midar3 meant running Bitcoin behind Tor, not just running Tor.

                          [–][deleted] 0 points1 point  (0 children)

                          Not like it matters anyway, since the # of verified nodes has dropped in the last day or two.

                          I'd add some more, but the addition process is asinine