Bitcoin Forum
September 20, 2017, 05:09:37 PM *
News: Latest stable version of Bitcoin Core: 0.15.0.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 [49] 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 »
  Print  
Author Topic: [announce] Namecoin - a distributed naming system based on Bitcoin  (Read 529298 times)
domob
Legendary
*
Offline Offline

Activity: 981


View Profile WWW
July 14, 2014, 05:30:50 AM
 #961

Well done domob, the vision becomes reality ... might be sending a tip to id/domob now it is so easy Wink
Thanks, I'm glad you (and others) like it! Smiley

Use your Namecoin identity as OpenID: https://nameid.org/
Donations: 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NCdomobcmcmVdxC5yxMitojQ4tvAtv99pY
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS | GPG 0xA7330737
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1505927377
Hero Member
*
Offline Offline

Posts: 1505927377

View Profile Personal Message (Offline)

Ignore
1505927377
Reply with quote  #2

1505927377
Report to moderator
1505927377
Hero Member
*
Offline Offline

Posts: 1505927377

View Profile Personal Message (Offline)

Ignore
1505927377
Reply with quote  #2

1505927377
Report to moderator
freedomno1
Legendary
*
Offline Offline

Activity: 1316


Activity: 9001 == OP


View Profile WWW
July 14, 2014, 07:56:15 AM
 #962

Namecoin wallet nice
Congrats it has been a long time coming and will certainly help usability Smiley

Searching for freedom, and believing in bitcoins ability to change the world
BTC Tip Jar 1EByjy9e4FeGZuTV4Rx5hbf4PnFt7jGh8M
kagawawa
Member
**
Offline Offline

Activity: 110


View Profile
July 14, 2014, 08:34:57 AM
 #963

Who are devs of Namecoin?

marcus_of_augustus
Legendary
*
Offline Offline

Activity: 2380



View Profile
July 14, 2014, 08:44:11 AM
 #964

Who are devs of Namecoin?

that's a moving target ... there are few of us, some come and go too. Some disappear forever Sad

deepceleron
Legendary
*
Offline Offline

Activity: 1512



View Profile WWW
July 16, 2014, 02:54:18 PM
 #965

Well done domob, the vision becomes reality ... might be sending a tip to id/domob now it is so easy Wink
Thanks, I'm glad you (and others) like it! Smiley

What is the spec of this, does it parse full JSONs, etc?

As an example, here is one of the first id namespaces, my id/deepceleron with a signed message:
{"info": "1DCeLERonUTsTERdpUNqxKTVMmnwU6reu5", "cert": {"address": "1DCeLERonUTsTERdpUNqxKTVMmnwU6reu5", "id": "deepceleron", "info": "deepceleron CA", "authority": "deepceleron", "authbtc": "1DCeLERonUTsTERdpUNqxKTVMmnwU6reu5", "authnmc": "N76D6hEHB55cGPk8QiG6ysgMbXb11b3nAH"}, "sig": "GweBRP+1YnKIMmXuwtsk4zlR7jUuPZxiazfNUbheGRMkomMs4lo/XpNpCDVLujrEynCGYe9dxs/M9nOp98EsXpI="}

As you can see, "info" is a Bitcoin address, and other stuff is inside a "cert", and that cert message is signed by the Bitcoin address.

phelix
Legendary
*
Offline Offline

Activity: 1680


nmc:id/phelix


View Profile
July 16, 2014, 07:36:20 PM
 #966

Well done domob, the vision becomes reality ... might be sending a tip to id/domob now it is so easy Wink
Thanks, I'm glad you (and others) like it! Smiley

What is the spec of this, does it parse full JSONs, etc?

As an example, here is one of the first id namespaces, my id/deepceleron with a signed message:
{"info": "1DCeLERonUTsTERdpUNqxKTVMmnwU6reu5", "cert": {"address": "1DCeLERonUTsTERdpUNqxKTVMmnwU6reu5", "id": "deepceleron", "info": "deepceleron CA", "authority": "deepceleron", "authbtc": "1DCeLERonUTsTERdpUNqxKTVMmnwU6reu5", "authnmc": "N76D6hEHB55cGPk8QiG6ysgMbXb11b3nAH"}, "sig": "GweBRP+1YnKIMmXuwtsk4zlR7jUuPZxiazfNUbheGRMkomMs4lo/XpNpCDVLujrEynCGYe9dxs/M9nOp98EsXpI="}

As you can see, "info" is a Bitcoin address, and other stuff is inside a "cert", and that cert message is signed by the Bitcoin address.
Nah, it directly uses the address that actually holds the name.

blockchained.com ■ bitcointalk top posts
freedomno1
Legendary
*
Offline Offline

Activity: 1316


Activity: 9001 == OP


View Profile WWW
July 17, 2014, 10:54:11 AM
 #967

Saw this in Bitcoin discussion seems interesting enough to post here since its a Trendmicro paper analyzing the namecoin project

Bitcoin Domains

http://www.trendmicro.com.au/cloud-content/us/pdfs/security-intelligence/white-papers/wp-bitcoin-domains.pdf


"This paper will attempt to explain what ADR TLDs are and describe the current scope of .bit domains, enumerate .bit domains’ weaknesses, and present a case study of a .bit Trojan and prospective malicious uses of .bit domains."

I'm curious about the botnet that is operating in the namecoin system and was wondering if you guys had any idea on that part of the paper and how it would be avoided.

The Trend Micro™ Smart Protection Network™, a cloud security infrastructure that rapidly and accurately identifies new threats and delivers global threat intelligence to secure data wherever it resides, detected a botnet that operates with .bit domains

I believe this is Circa 2013 based on Last access November 12, 2013 on the citations so if I missed the discussion feel free to correct or direct me to it.

Searching for freedom, and believing in bitcoins ability to change the world
BTC Tip Jar 1EByjy9e4FeGZuTV4Rx5hbf4PnFt7jGh8M
domob
Legendary
*
Offline Offline

Activity: 981


View Profile WWW
July 18, 2014, 07:25:34 PM
 #968

Well done domob, the vision becomes reality ... might be sending a tip to id/domob now it is so easy Wink
Thanks, I'm glad you (and others) like it! Smiley

Would there be any way of permitting access to fields? Ex: The ID and website address are accessible to anyone but other fields are only accessible by consent, someone has to have your permission via their own ID to view your email, phone number, etc. I was thinking something along the lines of levels of permission but entry by entry would probably be more versatile.

I can see some applications for this, but in principle, everything you have in the blockchain is public.  So the only way to achieve what you are asking about is to encrypt certain fields, and share the keys with selected people - or something along these lines.  One could probably work out the details, but so far, noone has stated interest in something like that.  Feel free to share any ideas you have, though. Smiley

Use your Namecoin identity as OpenID: https://nameid.org/
Donations: 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NCdomobcmcmVdxC5yxMitojQ4tvAtv99pY
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS | GPG 0xA7330737
phelix
Legendary
*
Offline Offline

Activity: 1680


nmc:id/phelix


View Profile
July 19, 2014, 08:11:06 PM
 #969

Secure anonymous voting with centralized identification entity: Entity hands out voting tokens (names) to verified IDs. Users do a couple rounds of coinjoin with the voting tokens whenever they feel like it. Vote through the token. Repeat for the next vote.

blockchained.com ■ bitcointalk top posts
BitPla.net
Jr. Member
*
Offline Offline

Activity: 31


View Profile WWW
July 20, 2014, 03:45:52 PM
 #970

________
nutildah
Legendary
*
Offline Offline

Activity: 826


Destroyer of Buffets


View Profile
July 22, 2014, 06:08:58 AM
 #971

I'm having a problem with the .conf file. Is there a special way it needs to be created? the way I was doing it was with a text document named bitoin.conf and I'd put a user name and pass in it yet it still doesn't work. Namecoind closes automatically by itself still and if I run namecoind commands in CMD I get this error:

error: You must set rpcpassword=<password> in the configuration file:
C:/Users/Edit/AppData/Roaming/Namecoin/bitcoin.conf

The file is in the correct place. I must be doing something wrong. Any ideas?

Most likely the file is having .txt appended to it by notepad.  How to check.

Open a command prompt
type
move C:/Users/Edit/AppData/Roaming/Namecoin/bitcoin.conf.txt C:/Users/Edit/AppData/Roaming/Namecoin/bitcoin.conf

Try to start bitcoind again

Hey this is the future calling (present... well past, now) and I just wanted to say thanks for posting this. Your advice helped my digital toy go. I'm glad the basics haven't changed much.

fredeq
Legendary
*
Offline Offline

Activity: 1240


View Profile WWW
July 30, 2014, 08:20:56 PM
 #972

Any block explorer with API for NMC?

Edit: Got it from other thread.

https://whattomine.com - Check what to mine Smiley | BTC: 1FanqAfDSCvQwzChwnvF3VGd9GTNV4n1tL | ETH: 0x932b9db891587dfae6f5d98cb27e7844a75160ba
nonnakip
Hero Member
*****
Offline Offline

Activity: 568



View Profile
August 19, 2014, 09:56:57 PM
 #973

namecoind (Linux) freaks out since a few days. 100% CPU. Unresponsive.

I debug problem and found mlock() is silently failing. Problem can be solved by increasing RLIMIT_MEMLOCK for the process.

Easy way to do this is from root shell: ulimit -l unlimited

Then start namecoind as a child process from the root shell. Preferably as a different user.

iCEBREAKER
Legendary
*
Offline Offline

Activity: 1778


http://DashNdrink.com


View Profile WWW
August 19, 2014, 11:46:43 PM
 #974

Relevant to our interests:

Using the mini-blockchain for decentralized DNS and encrypted internet layer
https://bitcointalk.org/index.php?topic=746100.msg8437811#msg8437811

I don't entirely understand BitFreak's proposal yet but it seems very impressive, with many fancy words and clever techno-magic!   Cool

The difference between bad and well-developed digital cash will determine whether we have a dictatorship or a real democracy.  David Chaum 1996
"Monero" : { Private - Auditable - 100% Fungible - Flexible Blocksize - Wild & Free® - Intro - Core GUI - Podcats - Roadmap - Dice - Blackjack - Github - Android }
MoneroForCash.com  |  Buy and sell XMR near you  |  Easymonero.com  |  Bitsquare.io - Decentralized XMR Exchange  |  Buy XMR with fiat
Fungibility provides privacy as a side effect.  Adam Back 2014

Bitcoin is intentionally designed to be ungovernable and governance-free.  luke-jr 2016
Blocks must necessarily be full for the Bitcoin network to be able to pay for its own security.  davout 2015
Blocksize is an intentionally limited resource, like the 21e6 BTC limit.  Changing it degrades the surrounding economics, creating negative incentives.  Jeff Garzik 2013


The raison d'être of bitcoin is trustlessness. - Eric Lombrozo 2015
It is an Engineering Requirement that Bitcoin be “Above the Law”  Paul Sztorc 2015
Resiliency, not efficiency, is the paramount goal of decentralized, non-state sanctioned currency -Jon Matonis 2015

Bitcoin is intentionally designed to be ungovernable and governance-free.  luke-jr 2016

Technology tends to move in the direction of making surveillance easier, and the ability of computers to track us doubles every eighteen months. - Phil Zimmerman 2013

The only way to make software secure, reliable, and fast is to make it small. Fight Features. - Andy Tanenbaum 2004
agentgreen420
Newbie
*
Offline Offline

Activity: 21



View Profile WWW
August 24, 2014, 04:10:23 PM
 #975

Namecoin wallpaper and stl. file for 3D printing now available for download
on http://www.bitpla.net/2014/07/namecoin-nmc.html

Now you can make your own physical Namecoin

http://i59.tinypic.com/2b5chj.jpghttp://i62.tinypic.com/2j1k8sx.jpg

Very interesting. Doesn't seem all that useful though.

http://metamarket.trade: Trustless Marketplaces
phelix
Legendary
*
Offline Offline

Activity: 1680


nmc:id/phelix


View Profile
August 27, 2014, 07:45:18 PM
 #976

Quote from: phelix
An entity (pool or exchange) is aggregating lots of low value outputs. As this is good for the system in regard to future pruning efforts it is currently causing client time outs for miners, thus they go offline a lot. The entity seems to own a lot of NMC so it probably is not a deliberate attack.

The transactions come in waves of a couple hundreds to thousands, they are 18kb (100 inputs) or 27kb (150 inputs) large. They only cost the relay fee / kb to relay. The functions underlying the RPC call "getauxblock" can take quite a long time to go through processing these.

What we are doing in the new version to fix the issue is caching input information necessary for the mining relevant RPC calls (thanks again Domob!). Also we will limit tx size to 20kb as it's worse with larger tx O(numberInputs * txSize) and increase the relay fee to 1/5 of the minTxFee.


Give the new version a shot if you are experiencing issues, it should be especially helpful to miners:
Github: https://github.com/namecoin/namecoin/tree/v0.3.76beta
Windows installer: Namecoin_v0.3.76beta_setup.exe 
    sha256: 6f23032d4365571b5133aa0a54c97407d46a71e13fb53927ebd50fc9e1be34ee
Changelog
x-post from https://forum.namecoin.info/viewtopic.php?p=12459#p12459

blockchained.com ■ bitcointalk top posts
coins101
Legendary
*
Offline Offline

Activity: 1386



View Profile
August 31, 2014, 01:25:06 PM
 #977

Sorry for generating spam on your thread. If you want me to delete it, please let me know.

Darkcoin now has around 900 decentralized nodes running its anonymity mixing system. After the coming update to release what is expected to be the last release candidate before open sourcing the anonymity aspect of the project, and the independent audit of the anonymity + overall code, the devs are considering developing an alternative to Tor using the nodes already up and the ones that are expected to join the new network.

Someone has suggested using namecoin for one of the possible aspects of the network:


About .drk and .mn registrations, why not integrating namecoins .bit domains into this coming darknet?
.bit domains have been around quite some time now, and it would be wise to cooperate between existing coins instead of trying to do everything yourself.

The problem with .bit domains has always been how do you make .bit domains visible in an ordinary browser?

For .bit domains there have appeared a few plugins:

www.meowbit.com
www.freespeechme.org

Still, everybody who wants to view .bit domains has to install a plugin, and that is a big hurdle.
If darktor/darknet were able to integrate .bit domains, that would be fantastic for both namecoin and darkcoin.

I suspect they just need to reach out to the DRK devs and community to see if something could be worked on jointly, or if DRK can provide a route on to the eventual network.

Traffic generates costs, as long as there is an incentive for MN I can't see why the DRK devs (I can't speak for them) would not take a look.

I haven't raised this with the DRK devs, so it may be a little premature to raise it here....but just wondering what the feedback might be on the possible fit.

Thanks.

mumung
Jr. Member
*
Offline Offline

Activity: 53


View Profile
August 31, 2014, 04:24:24 PM
 #978

Without being an technical expert I think the namecoin-integration would be a great thing.
Whatever gives namecoin more exposure and actually provides real use cases can only be of mutual benefit for all parties involved. I am not saying that namecoin has no real use cases yet, it just feels like it could use some external boost to make efforts easier use and for possible wider adoption. So far it feels
like nmc-developpers are dealing mostly with nitty-gritty stuff with a slight chance of not
seeing the bigger picture (no offense).

So, I am all for it for the benefit of both coins!
rav3n_pl
Legendary
*
Offline Offline

Activity: 1350


Don`t panic! Organize!


View Profile WWW
September 01, 2014, 09:39:01 AM
 #979

Any ideas wgo on network?
My daemon is eating 100% cpu and I see in log 18kb transactions over and over...
Code:
AcceptToMemoryPool(): accepted fd1f65b625
received: tx (18046 bytes)
AcceptToMemoryPool(): accepted a01bf0ec7f
received: tx (18047 bytes)
AcceptToMemoryPool(): accepted eaf29142f8
received: tx (18045 bytes)
AcceptToMemoryPool(): accepted d2d6894a27
received: tx (18052 bytes)
AcceptToMemoryPool(): accepted 42533f94fb
received: tx (18058 bytes)
AcceptToMemoryPool(): accepted 127021528d
received: tx (18045 bytes)
AcceptToMemoryPool(): accepted 15e0bd0ff2
received: tx (18051 bytes)
AcceptToMemoryPool(): accepted 357c7bf187
received: tx (18040 bytes)
AcceptToMemoryPool(): accepted f8c49ae806
received: tx (18037 bytes)
AcceptToMemoryPool(): accepted c49c93c47f
received: tx (18052 bytes)
AcceptToMemoryPool(): accepted ba866d0c43
received: tx (18043 bytes)
AcceptToMemoryPool(): accepted d5aea1af48
received: tx (18049 bytes)
AcceptToMemoryPool(): accepted d1e0e3e0c6
received: tx (18043 bytes)
AcceptToMemoryPool(): accepted 540dfae4d7
received: tx (18039 bytes)
AcceptToMemoryPool(): accepted bb61890670
received: tx (18043 bytes)
AcceptToMemoryPool(): accepted 46c88f8105
received: tx (18041 bytes)
AcceptToMemoryPool(): accepted a604b9f9cc
received: tx (18031 bytes)
AcceptToMemoryPool(): accepted 959514d7b1
received: tx (18042 bytes)
AcceptToMemoryPool(): accepted b3ddf9905e
received: tx (18041 bytes)
AcceptToMemoryPool(): accepted f377bc465a
received: tx (18029 bytes)
AcceptToMemoryPool(): accepted 1b9ad55c17
received: tx (18030 bytes)
AcceptToMemoryPool(): accepted 2de29a0c2b
received: tx (18041 bytes)
AcceptToMemoryPool(): accepted 46184e5ce1
received: tx (18047 bytes)
AcceptToMemoryPool(): accepted a2dad65a43
received: tx (18037 bytes)
AcceptToMemoryPool(): accepted a44e0047aa
received: tx (18045 bytes)
AcceptToMemoryPool(): accepted 26fcbc32e8
received: tx (18033 bytes)
AcceptToMemoryPool(): accepted 6fd30a0b4b
received: tx (18054 bytes)
AcceptToMemoryPool(): accepted 895f501ba0
received: tx (18054 bytes)
AcceptToMemoryPool(): accepted 2e454d0275
received: tx (18053 bytes)
AcceptToMemoryPool(): accepted b9883a16cc
received: tx (18036 bytes)
AcceptToMemoryPool(): accepted 08bbfd866f
received: tx (18046 bytes)
AcceptToMemoryPool(): accepted 39c050a575
received: tx (18049 bytes)
AcceptToMemoryPool(): accepted 24e0e443ed
received: tx (18042 bytes)
AcceptToMemoryPool(): accepted c5c4ef99b9
received: tx (18031 bytes)
AcceptToMemoryPool(): accepted d86fae2a2b
received: tx (18041 bytes)
AcceptToMemoryPool(): accepted c4895a4c4c
received: tx (18049 bytes)
AcceptToMemoryPool(): accepted 12778d538d
received: tx (18050 bytes)
AcceptToMemoryPool(): accepted 4f8644d442
received: tx (18046 bytes)
AcceptToMemoryPool(): accepted c26e83f6ac
received: tx (18039 bytes)
AcceptToMemoryPool(): accepted 500fe8315b
received: tx (18046 bytes)
AcceptToMemoryPool(): accepted 8cecbe9e9e
received: tx (18045 bytes)
AcceptToMemoryPool(): accepted e0984ffb07
received: tx (18046 bytes)
AcceptToMemoryPool(): accepted 6d113f20da
received: tx (18023 bytes)
AcceptToMemoryPool(): accepted b8fd16302d
received: tx (18047 bytes)
AcceptToMemoryPool(): accepted d7207c347b
received: tx (18040 bytes)
AcceptToMemoryPool(): accepted a491d330a2
received: tx (18042 bytes)
AcceptToMemoryPool(): accepted 20dd16ce10
received: tx (18037 bytes)
AcceptToMemoryPool(): accepted 073f064f05
received: tx (18040 bytes)
AcceptToMemoryPool(): accepted 8e0edd7cfb
received: tx (18045 bytes)
AcceptToMemoryPool(): accepted 78d93c9e9d
received: tx (18043 bytes)
AcceptToMemoryPool(): accepted daded960d4
received: tx (18043 bytes)
AcceptToMemoryPool(): accepted a5c6dbc95b
received: tx (18033 bytes)
AcceptToMemoryPool(): accepted e203ffe0d4
received: tx (18051 bytes)
AcceptToMemoryPool(): accepted 230c2ab4b0
received: tx (18041 bytes)
AcceptToMemoryPool(): accepted d23bac0ccf
received: tx (18040 bytes)
AcceptToMemoryPool(): accepted b5b60e6348
received: tx (18055 bytes)
AcceptToMemoryPool(): accepted d2b8a50004
received: tx (18058 bytes)
AcceptToMemoryPool(): accepted 892ac697be
received: tx (18030 bytes)
AcceptToMemoryPool(): accepted 23c4f65379
received: tx (18045 bytes)
AcceptToMemoryPool(): accepted 5c33139385
received: tx (18047 bytes)
Daemon is not responding on RPC calls and cant mine it on P2pool.

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
Some stuff on https://github.com/Rav3nPL/
phelix
Legendary
*
Offline Offline

Activity: 1680


nmc:id/phelix


View Profile
September 02, 2014, 07:10:09 PM
 #980

Any ideas wgo on network?
My daemon is eating 100% cpu and I see in log 18kb transactions over and over...
Code:
AcceptToMemoryPool(): accepted fd1f65b625
received: tx (18046 bytes)
AcceptToMemoryPool(): accepted a01bf0ec7f
received: tx (18047 bytes)
AcceptToMemoryPool(): accepted eaf29142f8
received: tx (18045 bytes)
AcceptToMemoryPool(): accepted d2d6894a27
received: tx (18052 bytes)
AcceptToMemoryPool(): accepted 42533f94fb
received: tx (18058 bytes)
AcceptToMemoryPool(): accepted 127021528d
received: tx (18045 bytes)
AcceptToMemoryPool(): accepted 15e0bd0ff2
received: tx (18051 bytes)
AcceptToMemoryPool(): accepted 357c7bf187
received: tx (18040 bytes)
AcceptToMemoryPool(): accepted f8c49ae806
received: tx (18037 bytes)
AcceptToMemoryPool(): accepted c49c93c47f
received: tx (18052 bytes)
AcceptToMemoryPool(): accepted ba866d0c43
received: tx (18043 bytes)
AcceptToMemoryPool(): accepted d5aea1af48
received: tx (18049 bytes)
AcceptToMemoryPool(): accepted d1e0e3e0c6
received: tx (18043 bytes)
AcceptToMemoryPool(): accepted 540dfae4d7
received: tx (18039 bytes)
AcceptToMemoryPool(): accepted bb61890670
received: tx (18043 bytes)
AcceptToMemoryPool(): accepted 46c88f8105
received: tx (18041 bytes)
AcceptToMemoryPool(): accepted a604b9f9cc
received: tx (18031 bytes)
AcceptToMemoryPool(): accepted 959514d7b1
received: tx (18042 bytes)
AcceptToMemoryPool(): accepted b3ddf9905e
received: tx (18041 bytes)
AcceptToMemoryPool(): accepted f377bc465a
received: tx (18029 bytes)
AcceptToMemoryPool(): accepted 1b9ad55c17
received: tx (18030 bytes)
AcceptToMemoryPool(): accepted 2de29a0c2b
received: tx (18041 bytes)
AcceptToMemoryPool(): accepted 46184e5ce1
received: tx (18047 bytes)
AcceptToMemoryPool(): accepted a2dad65a43
received: tx (18037 bytes)
AcceptToMemoryPool(): accepted a44e0047aa
received: tx (18045 bytes)
AcceptToMemoryPool(): accepted 26fcbc32e8
received: tx (18033 bytes)
AcceptToMemoryPool(): accepted 6fd30a0b4b
received: tx (18054 bytes)
AcceptToMemoryPool(): accepted 895f501ba0
received: tx (18054 bytes)
AcceptToMemoryPool(): accepted 2e454d0275
received: tx (18053 bytes)
AcceptToMemoryPool(): accepted b9883a16cc
received: tx (18036 bytes)
AcceptToMemoryPool(): accepted 08bbfd866f
received: tx (18046 bytes)
AcceptToMemoryPool(): accepted 39c050a575
received: tx (18049 bytes)
AcceptToMemoryPool(): accepted 24e0e443ed
received: tx (18042 bytes)
AcceptToMemoryPool(): accepted c5c4ef99b9
received: tx (18031 bytes)
AcceptToMemoryPool(): accepted d86fae2a2b
received: tx (18041 bytes)
AcceptToMemoryPool(): accepted c4895a4c4c
received: tx (18049 bytes)
AcceptToMemoryPool(): accepted 12778d538d
received: tx (18050 bytes)
AcceptToMemoryPool(): accepted 4f8644d442
received: tx (18046 bytes)
AcceptToMemoryPool(): accepted c26e83f6ac
received: tx (18039 bytes)
AcceptToMemoryPool(): accepted 500fe8315b
received: tx (18046 bytes)
AcceptToMemoryPool(): accepted 8cecbe9e9e
received: tx (18045 bytes)
AcceptToMemoryPool(): accepted e0984ffb07
received: tx (18046 bytes)
AcceptToMemoryPool(): accepted 6d113f20da
received: tx (18023 bytes)
AcceptToMemoryPool(): accepted b8fd16302d
received: tx (18047 bytes)
AcceptToMemoryPool(): accepted d7207c347b
received: tx (18040 bytes)
AcceptToMemoryPool(): accepted a491d330a2
received: tx (18042 bytes)
AcceptToMemoryPool(): accepted 20dd16ce10
received: tx (18037 bytes)
AcceptToMemoryPool(): accepted 073f064f05
received: tx (18040 bytes)
AcceptToMemoryPool(): accepted 8e0edd7cfb
received: tx (18045 bytes)
AcceptToMemoryPool(): accepted 78d93c9e9d
received: tx (18043 bytes)
AcceptToMemoryPool(): accepted daded960d4
received: tx (18043 bytes)
AcceptToMemoryPool(): accepted a5c6dbc95b
received: tx (18033 bytes)
AcceptToMemoryPool(): accepted e203ffe0d4
received: tx (18051 bytes)
AcceptToMemoryPool(): accepted 230c2ab4b0
received: tx (18041 bytes)
AcceptToMemoryPool(): accepted d23bac0ccf
received: tx (18040 bytes)
AcceptToMemoryPool(): accepted b5b60e6348
received: tx (18055 bytes)
AcceptToMemoryPool(): accepted d2b8a50004
received: tx (18058 bytes)
AcceptToMemoryPool(): accepted 892ac697be
received: tx (18030 bytes)
AcceptToMemoryPool(): accepted 23c4f65379
received: tx (18045 bytes)
AcceptToMemoryPool(): accepted 5c33139385
received: tx (18047 bytes)
Daemon is not responding on RPC calls and cant mine it on P2pool.
Please update to 0.3.76rc1

Unfortunately I think there are only binaries out yet for Windows...


blockchained.com ■ bitcointalk top posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 [49] 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!