The TMP Electrum plugin is what you want to easily generate lots of vendor addresses.
You need Electrum Bitcoin Wallet from here: https://electrum.org and the plugin (electrum_plugin.py) from the TMP forum here: http://themarketplace.i2p/forum/index.php?topic=83.0
I cover its installation if you're using Electrum wallet in the TAILS (Operating System) in version 0.5+ under "For TAILS (Linux) with Electrum". I'm afraid I haven't got a lot of time to go through it on other systems at the moment. The TMP forum is really helpful though, so if you get stuck, just fire off a question in there.
You can get the benefits of the Tails firewall if you run it in a virtual machine under windows. It won't protect you against keyloggers or other malware residing on your Windows box, though. It will, at least, let you experiment with Tails and protect you from clearnet data leaks.
Download VirtualBox for free from here:
These are the instructions for making a bootable USB for a Mac:
https://tails.boum.org/doc/first_steps/installation/manual/mac/index.en.html
Warning! These instructions are fairly involved and make use of the "dd" command. If you are not sure of what you are doing, you could easily overwrite your main disk drive and destroy all of your data.
"Necessary" is a strong word, "recommended" is probably a better choice. Chrome isn't completely open source, so nobody knows 100% what Google is or isn't collecting.
The best mix I've found so far of security + convenience for I2P is Firefox with the appropriate FoxyProxy patterns and the /r/privacy recommendations behind a paid VPN. There are of course numerous ways to get the job done.
I would admit, though, TAILS is probably a better option than my solution - just rather impractical and I think proper OpSec does more for you than any custom OS, plugin, VPN, etc.
Are there any other (web) wallets I can use? This Electrum way is too complicated. For me. uk_to's comment (https://www.reddit.com/r/themarketplace/comments/1vnywi/a_few_questions_about_buying_on_tmp/) looks so much easier than those other guides. Doesn't this work, too?
I installed Tails, which is an operating system, like Linux. Basically you start your Mac up off of cd. Once you take the CD out, all the info is erased and your safe. i2p is already on there, ready to go. I followed the instructions here: . Burn Tails onto a CD or DVD because a USB didn't work for me and my mac. I'm not computer expert, but I was able to figure this out after a few tries and a little Googling.
The other alternative is to use Firefox with NoScript and FoxyProxy. This is a little more risky but much easier to set up. You have to manually enter some proxy crap. As you can see, I'm not so sure about this method. But it doesn't require a different OS.
If you cannot remember / find your seed, you may still be able to decrypt your persistent volume. If I'm not mistaken, Tails uses a LUKS partition for encrypted persistence. Any system that supports LUKS should be able to decrypt your persistence volume.
Tails provides instructions on how to do that from another Tails instance here.
>It would be nice to be able to access the hundreds of dollars in my Electrum Wallet
I humbly suggest that, in the future, you not store hundreds of dollars in a wallet that you have not backed up. Hindsight is 20/20.
Actually, I found that you don't have to have persistence to use Electrum (it does mean you have to re-download it every time, but it doesn't take long). You can find owockEznan's instructions simplified for the average user here. I modified two things: instead of downloading the most recent version (1.9.6), I downloaded 1.8.1 (easier to configure network settings, in my opinion), and instead of doing the fourth command (using Tor as a proxy) from the command line, I did it manually from the wallet's network settings window.
You were doing it correctly. You don't have the key that is used to verify i2p packages.
Here is a modified version taht will solve your problem:
#!/bin/sh
apt-key list|grep -q i2p || curl https://geti2p.net/_static/debian-repo.pub | apt-key add -
apt-cache policy|grep -q i2p || echo 'deb http://deb.i2p2.no/ stable main' >> /etc/apt/sources.list apt-get update; apt-get install i2p i2p-keyring
Note that we are now relying on https (i.e., relying on the keys that are stored in /etc/ssl/certs
) instead of relying on i2p's own keys. So it's technically less secure. But it's good enough, really.
> If I had huge bandwidth resources and really wanted to find an eepsite I would just write a script to DoS/DDos every single i2p IP address and just wait until the eepsite went down.
… at which point you would know their i2p-address, not their Internet-IPV4 address.
An i2p address is just an ElGamal public key.
https://geti2p.net/en/docs/spec/common-structures#struct_Destination
Just as a test, disable the FoxyProxy addon in Firefox and manually enter the proxy settings:
In Windows Firefox it should be:
At the top left of the window hit the orange Firefox bar and then "Options".
Select "Network" tab then "Settings"
Select "Manual proxy configuration"
HTTP Proxy: 127.0.0.1 Port: 4444 SSL Proxy 127.0.0.1 Port: 4445
Restart the browser.
To my knowledge, you can't easily change what browser the I2P router console starts in, but you can turn it off so it doesn't open any browser on start. However, you can type that url in any browser and it will work fine. Your settings don't need to be setup correctly to access the router console.
Having your proxy settings set up correctly for I2P is needed to access i2p sites in your browser, but that has nothing to do with the I2P router console.
To set up FoxyProxy, you need to set a new proxy with settings 127.0.0.1 port 4444, and set the new pattern as
.i2p/
In your initial data you were wondering which of the proxy settings to use. It's the HTTP proxy setting you are concerned with right now.
In Windows Firefox it should be:
At the top left of the window hit the orange Firefox bar and then "Options".
Select "Network" tab then "Settings"
Select "Manual proxy configuration"
HTTP Proxy: 127.0.0.1 Port: 4444
If you have any proxy addons, like FoxyProxy, disable them for now. Just use the built-in Firefox proxy settings.
i2p in windows (as a service if desired), and FoxyProxy is all it takes to get there. Setting up a multi-sig wallet and gpgp is a bit more work, but rather simple once it's done.
Most people already figured out a normal wallet and pgp for the older marketplaces, so it's not a big leap, I think they'd want to avoid getting burned. Of course, there are different levels of drug users, and some of them ain't too smart.
What do you get when you put themarketplace.i2p into your Firefox address bar? What I mean by that is what does the page look like?
I think you might not be stuffing your Firefox traffic through the I2P router. The first thing to check is that the I2P bar looks like Step 7 in the "Installation & Configuration" section of the guide (stick http://127.0.0.1:7657/home into a Firefox tab once you've started I2P to check this). It should say: "Network: OK" (It might say "Network: WARN-{something} but that should also be ok) and "Accepting Tunnels" at the bottom. It may take a while after starting to get to this stage.
Finally, if both of those are golden and you've configured FoxyProxy correctly, right click the FoxyProxy icon on Firefox (It's a little foxes head on a button next to the address bar) and select "Use proxy "127.0.0.1:4444" for all URLs" - The foxes head should turn blue. Now stick TheMarketplace URL into your address bar (http://themarketplace.i2p) and see if that solves it (follow the rest of the steps in the guide to make sure).