sold! NB: it is a little more 'busy' in top right ... but isn't that one of those naturally discounted areas on the page so the little bit o' business draws the eye to it? ... or else 'tx' might not be consciously noted. W/E i like it. Edit: ooohhh , just set as desktop background and got a warm fuzzy feeling.  Edit2: wife just gave drive-by comment that she didn't read the 't' (on a laptop background sized image) on first glance ... had to do a double-take, stronger cross-bar for the t? totally up to you (she didn't have contacts in either  ) |
|
|
|
|
awesome .... superscript "txs" ? you forgot the 's'? or is not graphically aesthetic?
|
|
|
|
|
I might offer a bounty to the first instance of a picture/video of a bonafide grandma using a Trezor somewhere .... mmm, might have to be at retail location somewhere grandma like also.
|
|
|
|
|
I think people have got the power flow inverted in their minds ... power flows from the people ...
The correct question is "Do the regulators want to work with Bitcoin .... ?"
So far, it seems not.
|
|
|
|
No i don't have any problems with it. I test received 2 NMC today. How do i know this wallet is legit? How do i know if it doesn't nefariously steal my private key or send my NMC somewhere else by remote control?
We are testing and reviewing the namecoin-qt open source code, a branch of it is already in the official namecoin/namecoin repo for anybody's viewing pleasure. Seems pretty legit, but you are right to do due diligence |
|
|
|
Here are two more files. One is the world logo in a large png, the other is the same mockup but with the logo I think you're leaning towards. As you probably can tell, I'm very excited about this project lol.  I like this first logo v. much ... any chance we could get to see the above embossed one with the same background and "OPEN" but a superscript 'txs' instead of the "transactions" underlining? |
|
|
|
Lol well I was trying to figure out how much it is. The error should tell me that not the fee is 0.
Well as with everything for fees bitcoin-like ... "it depends" is the only correct answer. But you are right, it should not say fee is 0. |
|
|
|
With an empty wallet, trying to register a domain doesn't tell me how much I need, it just says fee is 0.
I use min tx fee of 0.005 and there is the name_new network fee of 0.01. The QT wallet quite cleverly sets aside 0.02 nmc so it can do the automatic name_firstupdate (12 blocks after name_new has a confirm). There maybe extra charges if your coins are made up of dusty outputs, etc ... I know for sure you cannot register a name with an empty wallet and have no idea why you would try, but hey, any testing is good. tl;dr If you have 0.02 nmc in your wallet you should be able to get a name registered. If you have nothing I can guarantee you will NOT get a name registered. |
|
|
|
<=============================  |
|
|
|
This looks like a really useful tool ... there are some concerns on the #namecoin irc [16:39] <randy-waterhouse> http://namecoin.com/[16:42] <Jeremy_Rand> randy-waterhouse: do you know if the source code for the namecoin.com Firefox/Chrome plugin is posted anywhere? [16:42] <echelon> d'oh.. whenever i looked up namecoin i got redirected to the dotbit website [16:42] <echelon> extensions are already open source aren't they? [16:42] <Jeremy_Rand> echelon: not necessarily, extensions can be obfuscated [16:44] <randy-waterhouse> Jeremy_Rand: good point, caution advised [16:44] <randy-waterhouse> hopefully namecoin.bit guy will post eventually [16:44] <randy-waterhouse> maybe waiting for first mover advantage to cement itself? [16:45] <randy-waterhouse> anyone know who is behiind namecoin.com ?? [16:46] <echelon> apparently this guy.. http://www.maayainfotech.com/[16:49] <echelon> interesting [16:49] <echelon> the extension is not obfuscated [16:49] <echelon> and it seems to retrieve this proxy auto-config file [16:49] <echelon> http://namecoin.com/extension/proxy.pac[16:49] <echelon> so the extension won't work if the domain is down [16:49] <echelon> and they could change it later on [16:49] <echelon> to do something more malicious [16:49] <Jeremy_Rand> ok, so the .pac file is hosted on a non-HTTPS domain [16:49] <echelon> yeah [16:50] <Jeremy_Rand> wonderful, so even if the operator is legit, some random guy on your network can install whatever pac file he wants onto your browser [16:50] <echelon> i dunno why they have to retrieve from the website anyway [16:50] <echelon> it could've been packaged with the extension [16:50] <Jeremy_Rand> yeah, suspicious |
|
|
|
 And mockup of logo on cardstock printed with spot uv.  This looks really great. I don't really like the colored ones, but the cardstock / spot uv looks amazing. Perhaps make a logo that looks more like the cardstock version? Also, can you make versions with TXS instead of TX in the upper corner? (Our command line tool is 'opentxs') I'd like to have the option of using it either way. I think I still have like .9 BTC laying around, so even though we're probably going with the other logo, I might still buy this one from you, if you are amenable to the price. It's just really cool. And if he rotated the 'O' through 180 degrees so that the the three sector dividers formed a slopey 'T' instead of upside down ... ? I like the silver embossed card look for the open^(txs) |
|
|
|
|
Is this more of a "gee whiz look what we could do" ... or is there someone actually doing something here?
nb: bitbills have been out of business for a long time, in internet years.
|
|
|
|
snailbrain: testing the latest branch and it looks like (from the debug.log) the name_new pop-up is creating the "Automatic name_firstupdate ... " transaction twice? Automatic name_firstupdate created for name d/bluewall, created tx: 5a6efa37eab3399d808365632257493d3313e47af8a7f5ed2e687205fe64cefb
sending: inv (37 bytes)
updateWallet da6f03cbfc3bbddf80a4451adab890435b47ebe35e764c32aa7ce77a5edefd8c 1
inWallet=1 inModel=1 Index=12-13 showTransaction=1 derivedStatus=1
updateWallet c41ad2083ef317d14400c8e1c829cf81470a8e4f29a8954ff69596becf834103 1
inWallet=1 inModel=0 Index=12-12 showTransaction=1 derivedStatus=0
updateWallet da6f03cbfc3bbddf80a4451adab890435b47ebe35e764c32aa7ce77a5edefd8c 1
inWallet=1 inModel=1 Index=13-14 showTransaction=1 derivedStatus=1
sending: inv (37 bytes)
sending: inv (37 bytes)
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes)
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes)
sending: inv (37 bytes)
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes)
sending: inv (37 bytes)
sending: inv (37 bytes)
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes)
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes)
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes)
sending: inv (37 bytes)
14/06/13 22:29:11 Flushing wallet.dat
Flushed wallet.dat 87ms
received: inv (37 bytes)
got inventory: tx c41ad2083ef317d14400 have
sending: inv (37 bytes)
keypool added key 134, size=101
keypool reserve 34
keypool keep 34
total value = 1500000
keypool added key 135, size=101
keypool reserve 35
keypool keep 35
Automatic name_firstupdate created for name d/bluewall, created tx: 156e4aa85ea82f56be91245bac112195e9f597c2ad5fa16692987648c298347f
and they have different tx number? Is this expected behaviour? Edit: I should say also that the automatic name_firstupdate worked and used the second TX number. I had another one that failed (I used the worng JSON syntax for the name so gui needs some error checking on this before form submission) and it showed as being completed in the TX list ... but sits there not confirming of course. I dug the rand: value out of debug.log (it shows up next to message about automatic name_firstupdate failure) and fixed it manually in debug console. |
|
|
|
The other bounty does seem much better organized. Is there anyone currently working on this bounty who would object to pledges here being transferred to ft's "holy grail" bounty?
This is what should properly happen ... I have the feeling that the original pledgers are not around any longer though  |
|
|
|
|
snailbrain and coder : 500nmc bounty sent for first tranche of namecoin-qt gui
ba41af08809cbe5b993b6313b4f9735efed3b60c3e5bdb3c1f4d9daa67249c0c
... for next tranche, debugging and merge into namecoin/namecoin master on github.
|
|
|
|
yeah, let's make this about the leaker because that really is the issue isn't it ...   I'm just wondering how a personal transaction-graph built up from all of this intercepted material is NOT a violation of 4th amendment? Doesn't that constitute a search? |
|
|
|
I'm hosting a full namecoin node on a raid0, but still this would be nice.
The switch to LevelDB in Bitcoin 0.8 really helped... but I guess it's a lot of work.
Hopefully not too much ... since bitcoin already did it and it is open source  |
|
|
|
Ummm, the facts are no-one can know the facts about these programs because they have placed themselves "legally" above scrutiny. The tech giants are legally bound to lie about any involvement so you cannot trust them and the secret court rulings on who does what are ... well secrets. The web of deceit is deep and tangled ... believe whatever 'facts' you like I guess. NSA is not above telling lies |
|
|
|
Meh. He doesn't get kudos from me for being a narcissist. Nor does his pole dancing girlfriend.
I have always assumed that the govt could intercept my fone calls etc. I'd laugh if they did. They'd probably be sitting their listening to elevator music while I'm on hold with my <cell/bank/university/health/whatever> company.
If this is the price I have to pay to significantly reduce the chance my legs will be blown off, then so be it. You're a complete idiot if you think it is about reducing the chances of "getting your legs blown off" ... and besides from 20 million to 1 down to 20.1 million to 1 ... worth it? You don't have to assume they are intercepting your 'fone' calls ... they ARE ... everyone one of them and they are storing them in a massive database for all time. It is not that there is some snivelly little NSA Stasi guy with headphones listening to your porn calls they just store them all up and data-mine the whole lot of them for when someone decides it is your turn to be gone after .... |
|
|
|
|
Show Posts
