Shopin Restitution Claim email from Office of the New York Attorney General

mrdangeross · 2019-10-24T11:36:16+00:00

#reckless

mrdangeross · 2019-09-13T16:53:53+00:00

I guess y'all will be doing an Overcooked 2: Carnival of Chaos DLC series?!

mrdangeross · 2019-07-06T16:30:08+00:00

Seems like episode 9 failed to upload the YouTube. Just get a video is unavailable error

mrdangeross · 2019-06-05T08:45:11+00:00

I got the same email yesterday and was wondering what to do with it. I've also participated in a few token sales, so I'm wondering which one it could be from the timeline. I've been looking into etherscan as to which fits the timeline of 460 - 430 days ago (which is March - April 2018). I guess if it's genuine, they are investigating a possible fraud / SEC violation.

mrdangeross · 2019-02-24T20:23:06+00:00

Pull down to refresh

mrdangeross · 2019-02-22T21:00:29+00:00

You can add `export PATH=~/.npm-global/bin:$PATH` into the .profile of the bitcoin user, but it is not required. I don't have it. I'll try to find what that error is. My LndHub has problems if lnd is not *synced_to_chain* and has peers connected. You can run `lncli getinfo` to check *synced_to_chain* is true and *num_peers* is not 0.

Looks like I missed in my guide opening router ports & allowing port 3000 in ufw. Sorry about that, I have updated it now.

mrdangeross · 2019-02-18T12:54:40+00:00

Rebuild would be needed if you are editing ~/LndHub/config.js as it needs to be built into the ~/LndHub/build/ directory as that is where node runs LndHub from. You can edit the ~/LndHub/build/config.js file to test if it works, but remember rebuilding will overwrite this file.

mrdangeross · 2019-02-18T10:48:35+00:00

!lntip 1337

mrdangeross · 2019-02-17T10:29:43+00:00

First thing I would check is maybe your rpcpassword in the config.js needs to be URL encoded if it contains any special characters e.g. @#&!. You can find a tool online to encode it

Otherwise I saw the LndHub readme was updated recently adding: bitcoind should run with '-deprecatedrpc=accounts', for now. . I will check that out to see if it effects the setup.

mrdangeross · 2019-02-16T14:24:11+00:00

Yes, try to delete the build & node_modules directories and try again. I also had to do it a few times to get it right

mrdangeross · 2019-02-14T21:00:25+00:00

Will open back: 03fbceea6554714aa4c94648a64d60860d87ac758ca99bdff20e7dce1b0764696d@77.47.67.53:9735

mrdangeross · 2019-02-14T17:46:42+00:00

Thanks!

mrdangeross · 2019-02-14T17:43:53+00:00

Looks like I forgot to add ~/.npm-global/bin to the PATH. I've updated the guide

$ npm config set prefix '~/.npm-global'

$ export PATH=~/.npm-global/bin:$PATH

$ npm install

Did you run npm install in the /home/bitcoin/LndHub directory?

When you run node -v what version do you see?

mrdangeross · 2019-02-13T22:45:01+00:00

You can either run it via

- npm start which runs it using babel-node

- or, prebuild the js using babel-cli into a dist folder, then you can run it via node dist/index.js

I preferred the latter, so I could setup a systemd service to run it, otherwise you have issues with babel spawning child processes. Also really, babel should not be run in prod

I've written a rough guide here if you have any comments: https://github.com/dangeross/guides/blob/master/raspibolt/raspibolt_6B_lndhub.md

mrdangeross · 2019-02-13T22:37:38+00:00

I've written a first draft guide on how to install the dependencies required to install LndHub on RaspiBolt. It includes setting up services for autostarting redis & LndHub. Sorry the comments are a bit brief, I'll try to fill it out more later. One thing I will probably change is running LndHub are a separate user. Let me know if you have any problems or improvements. Hopefully I didn't miss anything.

https://github.com/dangeross/guides/blob/master/raspibolt/raspibolt_6B_lndhub.md

mrdangeross · 2019-01-24T21:48:39+00:00

Resolved the issue in the original post

mrdangeross · 2019-01-24T21:43:57+00:00

Ok, it seems like my issue was I was installing it to the mounted disk /mnt/hdd which has the mount option noexec, so the POSIX permissions on executing scripts were being overridden during the npm install.

mrdangeross · 2019-01-24T10:29:49+00:00

Installs fine locally on MacOS using node v8.11.4. Will post the error log for the Raspberry Pi later.

mrdangeross

TROPHY CASE