News - Namecoin

User "libcoin" finds critical vulnerability in the Namecoin code allowing the attacker to renew names registered by somebody else (d/bitcoin and d/wav were overtaken as examples); the entire Namecoin dev-team organizes within hours to work on finding a solution!

submitted by HighBeamHater to Namecoin [link] [comments]

Namecoin devs are busy with Libcoin rebase

Just trying to keep everyone current on development, we are working hard on getting peripheral infrastructure (website, forum, wiki, DNS servers) as well as peripheral software (Firefox plugin, JavaScript/in-browser resolver, etc) so we are being kept REALLY busy. We also recently lost a developer to a stroke, which is personal setback for the team as a whole.
However, even with all of that, we are making swift progress on the Libcoin rebase. I'm not going to hold everyone else to any sort of deadline but I will say this: the core Namecoin implementation in Libcoin is already complete. We are working on porting the existing wallet and miner over.
The GUI will require a complete rewrite and we plan on making it entirely modular. This will take more time, but we are pushing everything to the RPC interface and since Libcoin comes with a SQLite, it will be significantly easier for developers to create user interfaces.
What's great about Libcoin is that it is much more modular than the mainline Bitcoin client. This significantly reduces the complexity of Namecoin specific code and we will be left with a maintainable code base. Like I said, I won't give any deadlines (I'm not even working on the C++ development!) but I will say that the estimates to catch the old code-base up to the current Bitcoin release was anywhere from 6-12 months.
submitted by indolering to Namecoin [link] [comments]

Dev Meeting Notes, 2016 07 03

#namecoin-meeting notes, 2016 07 03 # Present: Jeremy Jonas Samurai pigeons midnightmagic Decentralized Web Summit Jeremy attended DWS. Blog post summary is in PR. Note the new News layout / links, the Earlier News link, and the new post from June 20. Jonas ACKs. Namecoin Core Merged Mining Jorge Timon suggested replacing the MM chain ID with the BIP 122 chain ID. OS X Gitian Builds Jonas posted an OS X Gitian binary of Brandon's name tab PR Jonas will look into submitting a PR. Look into deterministically generating SDK input. PGP keys Jonas reminds everyone that we need to get our PGP keys into GitHub for Gitian. AAA hardfork Samurai asks if any problems expected short-term. Jeremy is pretty sure we're fine until Bitcoin schedules bit 0x100 for VersionBits. SegWit is bit 0x2. SPV Jeremy sent PR to libdohj. Currently undergoing review. Specs Jeremy posted draft Dehydrated Cert spec. Review would be appreciated. ncdns Jeremy noticed a bug in ncdns's JSON-RPC library that breaks connecting to the SPV client. Jeremy fixed it, but wonders why we're even using that library. It appears to be a very old library from Conformal that was abandoned over a year ago. Bring this up with Hugo (he didn't attend this meeting). Public Relations A bunch of website PR's have been ACKed by Jonas and merged by Jeremy. Jeremy added new "Donations" page to website. Jeremy added new FAQ to website. Funding libcoin-related bounties have been refunded by BountySource. BountySource balance: $5/month from 1 recurring supporter Total funds available: $299 USD NMDF incoming funds: 98.4 mBTC received since 2016 05 15 0 NMC received since 2016 05 15 
submitted by biolizard89 to Namecoin [link] [comments]

The next big thing - THE NEW INTERNET

Hide nmcontrol/namecoind windows on Windows
GNU/Linux users don't see the terminal windows for backend software; Windows users shouldn't be bothered by them either.
Don't try to visit .bit websites when blockchain isn't downloaded
Right now, visiting a .bit website with an incomplete blockchain will use an older version of that name's data. Usually this results in a failure to load the page with no good explanation of what's wrong, but in certain rare cases it could also hypothetically result in security issues such as hijacking. A better version of FreeSpeechMe should refuse to use incomplete blockchains.
Facilitate non-Firefox usage
FreeSpeechMe uses a networking method, HTTP, which is specific to website traffic. Replacing it with a different method, SOCKS, would make it much more flexible, so you could use Dot-Bit for non-website Internet applications such as SSH. It should also be possible to route other web browsers such as Chromium through FreeSpeechMe. FreeSpeechMe should support being installed as a standalone application for users who don't use Firefox (although obviously Firefox will remain the main method of installation).
Improvements for anonymous browsing
Right now FreeSpeechMe supports routing its traffic through anonymization proxies such as Tor and I2P (if they are installed), but it is not compatible with TorBrowser, so while attackers generally can't see your location or IP address, they can deduce that different activities you do online may have come from the same person. FreeSpeechMe should be improved to function in TorBrowser, which would prevent linkage of different online activities.
Improvements for anonymous hosting
FreeSpeechMe supports Tor and I2P hidden services (if the user has Tor or I2P installed), but does not support Freenet, OnionCat, GarliCat, or other anonymous hosting networks. This should be improved.
Support for next-gen TLS specification
FreeSpeechMe is using a method of specifying certificates to prevent hijacking which is deprecated in the Dot-Bit specification. While this method remains very secure, the newer specification has more features, and FreeSpeechMe should implement it.
HTTPS enforcement
Websites which claim to support HTTPS in their domain record should automatically be loaded in HTTPS, even if the user accidentally forgets the "s", to prevent hijacking in such cases. (Note for geeks: this is like the HSTS specification, but works even for sites you haven't visited before.)
Intelligent Redirecting
Websites that want to support Dot-Bit should be able to do so without changing their server configuration, and instead have FreeSpeechMe make the server think the preexisting domain is being requested. The user would still see the Dot-Bit URL in Firefox, and unlike iframe-based methods, the URL displayed in Firefox would change accordingly as the user clicks links..
Fix HTTP protocol bugs
Unencrypted HTTP Dot-Bit websites occasionally have odd behavior in FreeSpeechMe (sometimes manifesting as links not working properly); this is most frequently seen in WordPress websites. While we strongly encourage the use of HTTPS (which isn't subject to these bugs), we still want to fix the bugs with HTTP websites.
Round-Robin Load Balancing
Some large websites use multiple server IP addresses for a single domain. FreeSpeechMe should be able to randomly choose one.
Some of this is possibly out of the scope of this one Indiegogo campaign, depending on funds raised. But these are things we're very interested in helping implement:
Rebase on the latest Bitcoin code
Namecoin is based on an outdated version of Bitcoin (0.3.x). We should rebase on a current release. We inquired with a well-qualified and well-respected contractor (who developed Namecoin-Qt) about how much this rebase would cost; the estimate was around $17,000-$35,000 US. Spending that much on one project would be out of the realm of this first campaign. However, it may be possible to reduce this cost significantly by rebasing on a codebase other than Bitcoin, such as libcoin.
Improve scalability
Namecoin currently requires having the entire blockchain for good security. While the 1.6GB blockchain isn't a large concern right now, future scalability requires that clients be able to securely resolve names without possessing the blockchain. There is a proposal for this called SPV+UTXO.
Automatic renewal of names
Losing your names because you forgot to renew them is a problem.
Names should be able to be renewed automatically. Preferably without decrypting the wallet each time the name is renewed, and maybe without even needing your client to be open when it renews. Any solution must be trust-free.
Cold storage of Namecoin name keys
To update a Namecoin name, the keys must be decrypted on a computer with Internet access; this could be a security risk if malware is installed on that computer. To fix this, cold storage should be used, as is possible with Bitcoin.
This is in two parts: (1) port the Armory client to Namecoin (this allows transactions to be signed offline), and (2) allow a cold-storage name to be used as a revocation key for a hot-wallet name (this is called the "import" field).
Optimize Speed
Dot-Bit is already much faster than other top-level domains for both name lookup and name propagation. However, it can be made even faster.
We estimate that pre-cached name lookup time can be decreased by 2- to 5-fold in some cases, uncached name lookup time can be decreased significantly, name update propagation can be reduced from 40 minutes to under 1 minute, and blockchain sync time can be reduced significantly.
Android support
Namecoin software currently does not support Android; this situation should be improved.
Better blockchain anonymity
Like Bitcoin, Namecoin can keep the location and IP address of name owners anonymous (if used with Tor), but the various activities of name owners can be linked by an attacker. This should be improved, e.g. by implementing Zerocoin.
Better blockchain privacy
Some name owners may wish their records to not be publicly accessible; encryption would improve this situation.
Decentralized website single sign-on
Namecoin can be used to log into websites in a secure way without needing a password (protecting people from database leaks or cracked passwords without trusting a third party such as "all your data are belong to us" systems like Facebook); this is implemented as the NameID library by domob. Unfortunately, this library is not easy for non-programmers to integrate with existing websites. Plugins should be created for major website backends such as Drupal, phpBB, WordPress, and SMF, to allow trust-free NameID sign-on to be as easy as checking a box.
Automated builds
Namecoin software should support automated builds and testing so that our developers and testers can work more efficiently. The builds should also be deterministic (as Bitcoin and Tor are doing) to improve security.
Offline signing of static websites
Verifying signatures of static websites against the blockchain would prevent hijacking even if a web server is completely compromised.
SSH client integration
Log into your servers remotely without trusting your network or manually verifying fingerprints, using the same anti-hijacking features that FreeSpeechMe first implemented.
submitted by kitthecar to Bitcoin [link] [comments]

Matching Donations: Register/Manage Names with Libcoin Rebase / Lite Client

As you may know, the Namecoin dev team has been working to rebase namecoind and Namecoin-Qt on a newer codebase, specifically libcoin (a refactorization of Bitcoin Core by Michael Gronager of the Kraken exchange). This is because namecoind and Namecoin-Qt are based on the Bitcoin 0.3.x codebase, which is not really maintainable.
libcoin has a lot of nice benefits: most notably it makes it easier to produce trust-free lite clients (we've already done some experiments getting the stored blockchain reduced in size significantly, see ).
Right now libcoin does not support the name_new, name_firstupdate, and name_update RPC commands, which are a prerequisite to the rebase. (It already supports name_show, name_filter, and name_scan.) To help speed up development, the FreeSpeechMe fund will be matching donations for this feature 1:1 up to $50 USD (so up to $100 bounty total). The bounties are handled via BountySource; this means that no one can redeem the bounty until the GitHub issue is closed. BountySource's escrow services are built in to protect against fraud. Both USD and BTC are accepted by BountySource.
So, if you'd like to support Namecoin development and have a few dollars to spare, please consider posting a bounty. You can do so at the link below.
submitted by biolizard89 to Namecoin [link] [comments]

Free Cloud Mining Bitcoin, Litecoin, Dogecoin, Dash, Ethereum, Namecoin, Zcash, Peercoin What is Namecoin ? Bitcoin's First Altcoin ! - YouTube Altcoins (Bitcoin Alternatives) Defined and Explained in ... How To Convert Bitcoin Litecoin Namecoin Novacoin Terracoin Peercoin Feathercoin Primecoin To USD Bitcoin  Ethereum  Litecoin  Dogecoin  Ripple  Monero  Dash  Peercoin  Namecoin

Namecoin Core name_show name expiration. Aug 22, 2020 • yanmaani . Namecoin Core will, starting version 0.21, change the default behavior of the name_show RPC API call in the presence of certain errors to better match the documentation, the behavior of Electrum-NMC, and the behavior expected by users.. When Namecoin Core was first written, it exposed name resolution using an inconsistent API. Functionalities have been divided into logical units and libraries, minimizing dependencies for e.g. thin clients. > > libcoin is chain agnostic, all chain (bitcoin, testnet, namecoin, litecoin, ...) specific settings are maintained from a single class (Chain) and hence experiments with chain settings, mining, security and digital currencies ... Namecoin (Symbol: ℕ or NMC) is a cryptocurrency that is mined with bitcoin software as bonus. It is based on the code of bitcoin and uses the same proof-of-work algorithm. Like bitcoin, it is limited to 21 million coins. Unlike bitcoin, Namecoin can store data within its own blockchain transaction database.The original proposal for Namecoin called for Namecoin to insert data into bitcoin's ... Height: 265006: Version: 65795: Date/time: 2015-12-29 19:21:00: Difficulty: 29235432627.8: Number of transactions: 124: Output total: 937.8188047 NMC: Input total ... Namecoin (Symbol: ℕ oder NMC) ist eine Kryptowährung, die mit Bitcoin-Software als Bonus gewonnen wird.Es basiert auf dem Code von Bitcoin und verwendet den gleichen Proof-of-Work-Algorithmus.Wie Bitcoin ist es auf 21 Millionen Münzen begrenzt. Im Gegensatz zu Bitcoin kann Namecoin Daten in seiner eigenen Blockchain-Transaktionsdatenbank speichern.

[index] [6645] [7489] [14465] [5979] [5716] [16745] [30465] [25780] [8953] [4328]

Free Cloud Mining Bitcoin, Litecoin, Dogecoin, Dash, Ethereum, Namecoin, Zcash, Peercoin

In this video tutorial I will show you how to convert your Bitcoins and Litecoins into USD! ... Eobot Miner free program de minat Bitcoin,Dogecoin.Namecoin,Litecoin etc - Duration: 2:00 ... How To Convert Bitcoin Litecoin Namecoin Novacoin Terracoin Peercoin Feathercoin Primecoin To USD - Duration: 4:18. LuisTutorialTV 6,603 views. 4:18. Anton Kreil ... Minar Facil Bitcoin - Litecoin - BlackCoin - Namecoin - Dogecoin - NautilusCoin - Darkcoin - Vertcoin - BitSharesX - CureCoin - Peercoin - NXT - Syscoin. bitcoin bitcoin como funciona Namecoin (ℕ or NMC) is Bitcoin's First Altcoin - The cryptocurrency for decentralized .BIT domains. Bitcoin is a cryptocurrency and worldwide payment system. It is the first decentralized digital currency, as the system works without a central bank or single administrator. The network is peer-to ...