@doublec thanks for the modified polipo. What do you think about a modified resolver library that allows "sideloading"? How about this in /etc/resolv.conf:
I don't know much about DNS so avoided modifying or using any existing DNS code. What I have been able to do is get 'dnsmasq' to serve namecoind names using a standard dnsmasq build. eg. try: dig @cd.pn bluishcoder.bit This seems to work well. What I did was write a small program that does a name_scan and prints out the valid mappings in the same format as /etc/hosts. I then run dnsmasq with the option for obtaining names from this file. I have a script that runs every 5 minutes that rewrites this file and sends a SIGHUP to dnsmasq. The program to generate the hostfile is namecoin-hosts.c. It needs libjansson and libcurl. It can be built with: gcc -o namecoin-hosts namecoin-hosts.c -lcurl -ljansson The entries I changed in my dnsmasq.conf were: local=/.bit/
local-ttl=300
addn-hosts=/tmp/hosts.txt
I have a simple shell script that does the updating: while true; do
./namecoin-hosts 127.0.0.1:8332 rpcuser rpcpassword >/tmp/hosts.txt
kill -HUP `cat /var/run/dnsmasq/dnsmasq.pid`
echo `date`
sleep 300
done
|
|
|
|
So, with the current market rate at about 1.94, is my price considered fair? I'd preferably like to just sell it on MT Gox, but I'm Canadian and not willing to create a Liberty Reserve account. Anyways, let me know if you're interested, or if you've got some advice for a new guy I would love to hear it!
You might like to look into #bitcoin-otc - the 'over the counter' marketplace for buying and selling coins. |
|
|
|
|
I'd be interested too. Would #bitcoin-otc be a reasonable way of doing the trades? You can make use of the existing trust mechanism for example.
|
|
|
|
I hacked a bit on the polipo HTTP proxy code and added simple namecoin support for DNS lookups. The modified code is in this git repository: https://github.com/doublec/namecoin-polipo. It needs libjansson for JSON parsing and libcurl for talking to the namecoind JSON-RPC server. Once compiled, you can run it passing it the details about the namecoind server: $ git clone https://github.com/doublec/namecoin-polipo
$ cd namecoin-polipo
$ make
$ ./polipo namecoindServer="127.0.0.1:8332" namecoindUsername=rpcuser namecoindPassword=rpcpassword
This will start the proxy, and it'll connect to the namecoind JSON-RPC server with the given details. It runs 'name_scan' to get the list of names. Any program using this proxy will have all .bit domains resolved by namecoind. Currently it only supports mapping to IP addresses. So namecoind values like the following work: {"map":{"":"192.0.32.10"}}. As an example 'bluishcoder.bit' hopefully resolves to the IP address of my server with my weblog using this version of polipo. It rescans namecoind when a request is made for a domain lookup and the last scan was more than 10 minutes ago. To use it with Firefox (or other browsers) go into the network settings and set the 'http proxy' to localhost, port 8123. I decided to do this to avoid needing to run the ncproxy script since I don't need socks support. Comments, suggestions, patches are welcome. |
|
|
|
Until a DNS proxy that uses namecoin comes along, one approach to using namecoin for host name lookups could be to provide the option to scan the names every time a block is mined and update/rewrite the users /etc/hosts (or windows equivalent). This might be a quick way of starting to use the namecoin chain for lookups. Even a simple script that does this every 10 minutes or so, getting the names from namecoind via RPC would do a reasonable job.
An option for using socks enabled programs is to use ncproxy combined with SSH. SSH to localhost using the '-D' option to set up a socks proxy. $ ssh -Dn 2001 user@locahost &
$ ncproxy --user=namecoind-user --password=namecoind-password -p 9055 -s 127.0.0.1:2001
This sets up ncproxy to forward to the SSH proxy. You can configure firefox to use this socks proxy by going into 'Preferences/Advanced/Network/Settings' and adding '127.0.0.1' and '9055' in the Socks proxy area. You should also go into 'about:config' in Firefox, search for net.proxy.socks_remote_dns and double click on it to set it to true. This will cause DNS requests to go through ncproxy and then the SSH socks proxy. You can also slip polipo in there if you want a web cache. Run: $ ssh -Dn 2001 user@locahost &
$ ncproxy --user=namecoind-user --password=namecoind-password -p 9055 -s 127.0.0.1:2001
$ ./polipo socksParentProxy=localhost:9055
Configure firefox to use the HTTP proxy on port 9055 instead of a socks proxy. These approaches seem to work in that name lookups occur. Unfortunately there appear to be no namecoin entries with the JSON format to actually see if ncproxy is doing the job. |
|
|
|
|
Until a DNS proxy that uses namecoin comes along, one approach to using namecoin for host name lookups could be to provide the option to scan the names every time a block is mined and update/rewrite the users /etc/hosts (or windows equivalent). This might be a quick way of starting to use the namecoin chain for lookups. Even a simple script that does this every 10 minutes or so, getting the names from namecoind via RPC would do a reasonable job.
|
|
|
|
Will be an update here? It will be great if gethashespersec will show total hashps for all connected miners.  I added this to puddinpop's code in a branch of my github repository mirroring his code: https://github.com/doublec/bitcoin-pool/tree/lowcpuWith this code 'gethashespersec' will show the total server hash rate. It also adds a command line option '-distributionpercent' allowing the server operator to set the percentage of the generated coins that are available for distribution (the rest go to the server operator). It rounds the generated coin amounts to 3dp as well to help prevent dust accumulation in miners wallets. Feel free to cherry-pick the commits that interest you. |
|
|
|
|
I compiled namecoind on linux by just running 'make'. Not 'make -f makefile.unix' as you'd do to build 'bitcoind'. I also added 'rpcport=...' in the '~/.namecoin/bitcoin.conf' file to set an RPC port that doesn't clash with bitcoind that I have running. Note that the configuration file is still called 'bitcoin.conf' but it lives in '~/.namecoin'.
|
|
|
|
No problem with that, by November hopefully 100 BTC will be worth quite large amount of money. That's true, hopefully people contributing to the bounty put the bitcoins aside now while it's worth less I have a WP7 which is why I'm asking the questions btw, not trying to put 'stop energy' into the discussion. |
|
|
|
This bounty shouldn't be too hard, once bitcoinj has been developed, porting over to C# shouldn't be toohard. Then a WPF GUI needs to be made, and some sort of way to download/send transactions over http needs to be developed.
There's also the fact that Windows Phone 7 doesn't allow background processing or multitasking. Whenever you switch away from the app it stops. You'll have to download newest blocks everytime you start it. Again the november 'mango' update should help with this as some form of background operation is supposed to be available. I don't see any chance of your bounty being claimed if only a completely client side solution is allowed until at least mango becomes available in November-ish (earlier to registered WP7 developers possibly). |
|
|
|
Full client, except generation and JSON-RPC
da2ce7: 100BTC
It's not possible to do a full client on Windows Phone 7 at this stage. The public API's do not include socket access. Only HTTP requests are allowed. A workaround would need to be done whereby it accesses a client or proxy running on a server. Would that be adequate for the bounty? In the upcoming 'mango' update due about November for WP7 it will be possible to do socket level access. |
|
|
|
So I'm looking to get some Bitcoin, any Kiwi around willing to sell?
I'll pay via bank transfer, with Bitcoins in escrow (seller pays).
I can sell for bank transfer to an NZ account (or trade in person so we don't need escrow depending on where you are). I'd be looking to get around 1.07 NZD per BTC though depending on NZ exchange rate at the time. Look me up on #bitcoin-otc or PM me if you're interested. |
|
|
|
|
It looks like at some point your remote machine had a commit that the local or gitorious didn't have. Now every pull from your remote machine is a merge.
|
|
|
|
Wow, nice method for coming off as mature.
I'm not sure what your issue with sgornick's post is. Compute4Cash is a bitcoin pool and they pay to paypal. They are just targeting a different audience than bitcoin users. |
|
|
|
Is there no BitCoin2PayPal, where you send BitCoins to a BitCoin address, wait for a confirmation and around 10 minutes later the money is PayPal'd to you?
CoinCard pretty much does this. |
|
|
|
Now Firefox uses a SERVICE in windows.
Still, it opens slow to me than chrome. Even though i used speedyfox or starterfox.
Firefox does not use a windows service. Are you sure the third party addon starterfox isn't adding one? |
|
|
|
Btw, when i do bitcoind stop it seems it doesn't close (i still see it running with htop, and trying to fire it up again gives me an error about the .lock), am i doing somthing wrong?
It takes quite a while (a few minutes) to stop but it does eventually. I don't know why. |
|
|
|
Bitcoin opens an IRC connection to lfnet for bootstrapping (finding peers). New nodes have to find out about existing nodes somehow.
Run it with '-no-irc' to prevent it from making an IRC connection. You can also use '-no-listen' to prevent it from listening for incoming connections and use '-connect' to explicitly connect to a node. This minimizes the number of connections to your phone. |
|
|
|
|
Show Posts
