Bitcoin Forum
June 03, 2020, 11:32:24 PM *
News: Latest Bitcoin Core release: 0.19.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 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 71 72 73 74 [75] 76 77 78 79 80 81 82 83 84 85 86 87 88 89 »
  Print  
Author Topic: [announce] Namecoin - a distributed naming system based on Bitcoin  (Read 585240 times)
trantute2
Hero Member
*****
Offline Offline

Activity: 728
Merit: 504



View Profile
April 17, 2018, 07:01:12 PM
 #1481

Hmm ... I get a similar error:

Code:
{"jsonrpc":"1.0","id":"curltext","error":{"code":0,"message":"Server returned HTTP response code: 500 for URL: https://namecoin.webbtc.com/name/d/domob.json?history&with_height&with_rawtx&with_mrkl_branch&with_tx_idx&raw","data":{"exceptionTypeName":"java.io.IOException","message":"Server returned HTTP response code: 500 for URL: https://namecoin.webbtc.com/name/d/domob.json?history&with_height&with_rawtx&with_mrkl_branch&with_tx_idx&raw"}}}

Check the terminal, where namecoinj is running while the curl command is executed. There might be an exception, including "HTTP response code: 500" (see below), which in my case correlates with the curl command. I think, there lies the dog buried.

Code:
java.lang.reflect.InvocationTargetException: null
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_162]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_162]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_162]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_162]
at com.googlecode.jsonrpc4j.JsonRpcServer.invoke(JsonRpcServer.java:513) [jsonrpc4j-1.1.jar!/:na]
at com.googlecode.jsonrpc4j.JsonRpcServer.handleObject(JsonRpcServer.java:384) [jsonrpc4j-1.1.jar!/:na]
at com.googlecode.jsonrpc4j.JsonRpcServer.handleNode(JsonRpcServer.java:293) [jsonrpc4j-1.1.jar!/:na]
at com.googlecode.jsonrpc4j.JsonRpcServer.handle(JsonRpcServer.java:230) [jsonrpc4j-1.1.jar!/:na]
at com.googlecode.jsonrpc4j.JsonRpcServer.handle(JsonRpcServer.java:207) [jsonrpc4j-1.1.jar!/:na]
at com.googlecode.jsonrpc4j.spring.JsonServiceExporter.handleRequest(JsonServiceExporter.java:40) [jsonrpc4j-1.1.jar!/:na]
at org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter.handle(HttpRequestHandlerAdapter.java:51) [spring-webmvc-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:967) [spring-webmvc-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:901) [spring-webmvc-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970) [spring-webmvc-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:872) [spring-webmvc-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:661) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846) [spring-webmvc-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) [tomcat-embed-websocket-8.5.15.jar!/:8.5.15]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99) [spring-web-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:105) [spring-web-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.springframework.web.filter.HiddenHttpMethodFilter.doFilterInternal(HiddenHttpMethodFilter.java:81) [spring-web-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:197) [spring-web-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:478) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:80) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:799) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:861) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1455) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_162]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_162]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-8.5.15.jar!/:8.5.15]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_162]
Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://namecoin.webbtc.com/name/d/domob.json?history&with_height&with_rawtx&with_mrkl_branch&with_tx_idx&raw
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1894) ~[na:1.8.0_162]
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) ~[na:1.8.0_162]
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263) ~[na:1.8.0_162]
at java.net.URL.openStream(URL.java:1045) ~[na:1.8.0_162]
at com.fasterxml.jackson.core.JsonFactory._optimizedStreamFromURL(JsonFactory.java:1547) ~[jackson-core-2.8.8.jar!/:2.8.8]
at com.fasterxml.jackson.core.JsonFactory.createParser(JsonFactory.java:783) ~[jackson-core-2.8.8.jar!/:2.8.8]
at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2797) ~[jackson-databind-2.8.8.jar!/:2.8.8]
at org.libdohj.names.NameLookupLatestRestMerkleApi.getUntrustedNameHistory(NameLookupLatestRestMerkleApi.java:130) ~[libdohj-namecoin-0.14-SNAPSHOT.jar!/:na]
at org.libdohj.names.NameLookupLatestRestMerkleApi.getLatestUntrustedNameData(NameLookupLatestRestMerkleApi.java:103) ~[libdohj-namecoin-0.14-SNAPSHOT.jar!/:na]
at org.libdohj.names.NameLookupLatestRestMerkleApi.getNameTransaction(NameLookupLatestRestMerkleApi.java:63) ~[libdohj-namecoin-0.14-SNAPSHOT.jar!/:na]
at org.namecoin.bitcoinj.spring.service.NameLookupService.name_show(NameLookupService.java:157) ~[bitcoinj-server-0.2.7-SNAPSHOT.jar!/:na]
... 55 common frames omitted

I did not set the environment variable as recommended in the instructions. And I used OpendJDK.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1591227144
Hero Member
*
Offline Offline

Posts: 1591227144

View Profile Personal Message (Offline)

Ignore
1591227144
Reply with quote  #2

1591227144
Report to moderator
1591227144
Hero Member
*
Offline Offline

Posts: 1591227144

View Profile Personal Message (Offline)

Ignore
1591227144
Reply with quote  #2

1591227144
Report to moderator
1591227144
Hero Member
*
Offline Offline

Posts: 1591227144

View Profile Personal Message (Offline)

Ignore
1591227144
Reply with quote  #2

1591227144
Report to moderator
trantute2
Hero Member
*****
Offline Offline

Activity: 728
Merit: 504



View Profile
April 17, 2018, 07:07:52 PM
 #1482

Okay ...

Code:
export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64

... makes no difference.

I will stop here for today since I have to get up early in the morning tomorrow. And two beers are waiting ...

Maybe we should also try Oracle's java?
trantute2
Hero Member
*****
Offline Offline

Activity: 728
Merit: 504



View Profile
April 17, 2018, 07:30:28 PM
 #1483

One last thing for today: See

https://en.wikipedia.org/wiki/List_of_HTTP_status_codes

for the 500 error. It says:

Quote
500 Internal Server Error
    A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

(also compare it with https://de.wikipedia.org/wiki/HTTP-Statuscode)

Maybe it is not our fault. Maybe the server, the curl command is aiming for, is down or similar. But this is only one hypothesis.

And I have to admit, that I do not understand the curl command yet.
d5000
Legendary
*
Offline Offline

Activity: 2478
Merit: 1838


Decentralization Maximalist


View Profile
April 17, 2018, 08:32:38 PM
 #1484

Maybe it is not our fault. Maybe the server, the curl command is aiming for, is down or similar. But this is only one hypothesis.
That is also my hypothesis, as I checked the link to the webbtc block explorer in the error message and I get the same HTTP 500 error in a browser.

But ... if all what the "light client" does is to connect to a single, centralized block explorer to show the status of a name, what is its purpose? I could use curl, wget or another tool connecting directly to the block explorer and would need no light client. And the light client does download a part of the blockchain.

So I guess that there is some additional configuration step I didn't see, to ensure the light client checks several nodes for the required information (and not only the webbtc node). However, in the documentation, the URL of the webbtc block explorer is also mentioned several times.

Quote
And I have to admit, that I do not understand the curl command yet.
The curl command basically does what the "name_show" command of the namecoin-cli program would do (it basically shows who registered a domain/name, see here), only that you send it in JSON format directly to the "server" (in this case, your light client acts as a server).

By the way: Just read this reddit message - it seems that electrum-nmc isn't dead and is intended to be used in the future for name registrations. Maybe it's - once ready - a better choice for end users than the difficult-to-use consensusj client, but it should at least upgraded to v3.0.5 because of the vulnerability.

trantute2
Hero Member
*****
Offline Offline

Activity: 728
Merit: 504



View Profile
April 20, 2018, 06:45:32 AM
 #1485

But ... if all what the "light client" does is to connect to a single, centralized block explorer to show the status of a name, what is its purpose? I could use curl, wget or another tool connecting directly to the block explorer and would need no light client. And the light client does download a part of the blockchain.

True. Do you know where the blockchain is stored on the HD?

So I guess that there is some additional configuration step I didn't see, to ensure the light client checks several nodes for the required information (and not only the webbtc node). However, in the documentation, the URL of the webbtc block explorer is also mentioned several times.

Yes. And I still do not understand, what the tool is good for.

The curl command basically does what the "name_show" command of the namecoin-cli program would do (it basically shows who registered a domain/name, see here), only that you send it in JSON format directly to the "server" (in this case, your light client acts as a server).

In the description, it sounds like you can use namecoinj (for simplicity i will call it namecoinj) together with namecoin-cli. What is the benefit of that? Could it be, that namecoinj does not download the domain data? I played around with bitcoinj a few years ago to build my own wallet. It's quite easy to use. As far as I know, a light client only downloads the block headers, right (https://en.bitcoin.it/wiki/Thin_Client_Security )? And maybe, the domain data is not stored in the headers. That is, namecoinj is simply a namecoin wallet. For domain resolution, it needs a namecoin block explorer.  Huh Huh Huh
d5000
Legendary
*
Offline Offline

Activity: 2478
Merit: 1838


Decentralization Maximalist


View Profile
April 20, 2018, 10:04:07 AM
 #1486

True. Do you know where the blockchain is stored on the HD?
In my case the client created a sub-directory called LibdohjNameLookupDaemon.spvchain (in the same directory where the JAR file is located) and it seems to contain the (partial) blockchain.

Quote
Could it be, that namecoinj does not download the domain data? [...] That is, namecoinj is simply a namecoin wallet. For domain resolution, it needs a namecoin block explorer.  Huh Huh Huh
Seems so. But finally, I think I found the solution: If one doesn't want to rely on a block explorer one must use the following command line argument:

Code:
--namelookup.latest.algo=leveldbtxcache

This creates a name database on the HD based of the informations in full blocks (not just headers), it will sync a bit longer.

Here is a forum thread about the light client, that gave me the right clue.

BTW: the webbtc url continues to throw "Internal Server Error" for me. So it seems it isn't a temporary failure.

trantute2
Hero Member
*****
Offline Offline

Activity: 728
Merit: 504



View Profile
April 20, 2018, 06:05:21 PM
 #1487

True. Do you know where the blockchain is stored on the HD?
In my case the client created a sub-directory called LibdohjNameLookupDaemon.spvchain (in the same directory where the JAR file is located) and it seems to contain the (partial) blockchain.

Quote
Could it be, that namecoinj does not download the domain data? [...] That is, namecoinj is simply a namecoin wallet. For domain resolution, it needs a namecoin block explorer.  Huh Huh Huh
Seems so. But finally, I think I found the solution: If one doesn't want to rely on a block explorer one must use the following command line argument:

Code:
--namelookup.latest.algo=leveldbtxcache

This creates a name database on the HD based of the informations in full blocks (not just headers), it will sync a bit longer.

Here is a forum thread about the light client, that gave me the right clue.

BTW: the webbtc url continues to throw "Internal Server Error" for me. So it seems it isn't a temporary failure.

Cool. I will try it out tomorrow. Do you know some bit-domains or some site for browsing bit-domains so that I can play around with the name resolution? Thanks in advance.
d5000
Legendary
*
Offline Offline

Activity: 2478
Merit: 1838


Decentralization Maximalist


View Profile
April 20, 2018, 07:24:04 PM
 #1488

Cool. I will try it out tomorrow. Do you know some bit-domains or some site for browsing bit-domains so that I can play around with the name resolution? Thanks in advance.
Try http://nf.bit (Namecoin forum) and http://nx.bit (Blockchained.com). Both still work.

There is a (pretty old) list here.

I today earlier tried out the leveldbtxcache option and it didn't work (it threw a "Connection refused" error) but it's well possible that the blockchain part that is needed for name resolution wasn't fully downloaded.

rainypu
Newbie
*
Offline Offline

Activity: 96
Merit: 0


View Profile
April 26, 2018, 04:55:44 PM
 #1489

Hi guys. I have been interested in Namecoin for quite some time, but I'm not sure of exactly who are the relative representatives (assuming Coblee would be for Litecoin, Gavin would be for Bitcoin, etc).
mt55
Sr. Member
****
Offline Offline

Activity: 448
Merit: 250


View Profile
April 29, 2018, 12:24:31 AM
 #1490

Namecoin has many useful functions, therefore it is impossible to consider it simply as an ordinary coin. It is an innovation that will show itself to the world. I read information about the Safinus project as an investment platform. I also see a lot of revolutionary innovations there

Namecoin also has an incredible history in the crypto space. I hope it can go back up again as it is one of the oldest coins out there!
I agree in many respects with you and your opinion. Now probably have to still look and technology that will be in demand in the future. But this coin test of time and I think it is still manifest themselves in the future.

True though that the technology also needs to advance as it also does for other coins with active development. Standing the test of time is one thing, active development the other.
versprichnix
Sr. Member
****
Offline Offline

Activity: 843
Merit: 287


View Profile
April 29, 2018, 10:10:43 AM
 #1491

Hi guys. I have been interested in Namecoin for quite some time, but I'm not sure of exactly who are the relative representatives (assuming Coblee would be for Litecoin, Gavin would be for Bitcoin, etc).

It's decentralised, so there's no single "god" for namecoin. This increases the propability to survive attacks.
d5000
Legendary
*
Offline Offline

Activity: 2478
Merit: 1838


Decentralization Maximalist


View Profile
April 29, 2018, 08:23:49 PM
 #1492

True though that the technology also needs to advance as it also does for other coins with active development. Standing the test of time is one thing, active development the other.
There is active development.  I've already mentioned the ConsensusJ light client.

The full client, namecoin-core follows Bitcoin development closely, the last update was 7 days ago.

The problem, for me, is still usability. It is still too difficult for the "general public" to use Namecoin. The Blockchain DNS project (browser extensions) I mentioned earlier is a big step forward as it works on two of the most popular browsers and works out-of-the-box. I think porting the Blockchain DNS extension to the remaining browsers (Safari and Edge/IE) and with a stable light client (ConsensusJ or Electrum) Namecoin can be a success.

trantute2
Hero Member
*****
Offline Offline

Activity: 728
Merit: 504



View Profile
May 07, 2018, 08:52:20 PM
Last edit: May 11, 2018, 05:15:00 AM by trantute2
Merited by d5000 (1)
 #1493

True though that the technology also needs to advance as it also does for other coins with active development. Standing the test of time is one thing, active development the other.
There is active development.  I've already mentioned the ConsensusJ light client.

The full client, namecoin-core follows Bitcoin development closely, the last update was 7 days ago.

The problem, for me, is still usability. It is still too difficult for the "general public" to use Namecoin. The Blockchain DNS project (browser extensions) I mentioned earlier is a big step forward as it works on two of the most popular browsers and works out-of-the-box. I think porting the Blockchain DNS extension to the remaining browsers (Safari and Edge/IE) and with a stable light client (ConsensusJ or Electrum) Namecoin can be a success.

Since you mention that: I stumbled over the signatures (https://github.com/namecoin/gitian.sigs) of the current namecoin version (https://namecoin.org/download/) which obviously is 0.13.99.

There are also signatures for version 0.15.99! Does anyone know more?

As a finger exercise:

How to use those signatures? (Because it always works a little bit different for each project (here I stay with version 0.13.99). E.g. BitcoinUnlimited signs hash sums via Bitcoin's message signature system, which is only consequent: https://www.bitcoinunlimited.info/download. Some projects do not even provide signatures.)

Firstly download the software, e.g. via

Code:
wget https://namecoin.org/files/namecoin-core-0.13.99-name-tab-beta1-notreproduced/namecoin-0.13.99-i686-pc-linux-gnu.tar.gz

Then import the corresponding gpg-key:

Code:
gpg --keyserver keyserver.ubuntu.com --recv F8F7BF85

Which returns something similar to:

Code:
gpg: requesting key F8F7BF85 from hkp server keyserver.ubuntu.com
gpg: key F8F7BF85: public key "Jeremy Rand (Master Key) <jeremy@veclabs.net>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)

You can find the key here:

https://keyserver.ubuntu.com/pks/lookup?op=vindex&search=JeremyRand&fingerprint=on

Via searching for "JeremyRand" at

https://keyserver.ubuntu.com/

Then, you must clone the signature repository of namecoin

Code:
git clone https://github.com/namecoin/gitian.sigs.git

And enter the corresponding directory

Code:
cd gitian.sigs/0.13.99-name-tab-beta1-linux/JeremyRand/

Check the signature

Code:
gpg --verify namecoin-linux-0.13-build.assert.sig

Which returns

Code:
gpg: assuming signed data in `namecoin-linux-0.13-build.assert'
gpg: Signature made Sa 15 Okt 2016 22:13:13 CEST using RSA key ID 786D6570
gpg: Good signature from "Jeremy Rand (Master Key) <jeremy@veclabs.net>"
gpg:                 aka "Jeremy Rand <jeremy.rand@ou.edu>"
gpg:                 aka "Jeremy Rand <jeremy@namecoin.org>"
gpg:                 aka "Jeremy Rand <biolizard89@gmail.com>"
gpg:                 aka "Jeremy Rand <jeremyrand@airmail.cc>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 5174 0B7C 732D 572A 3140  4010 6605 55E1 F8F7 BF85
     Subkey fingerprint: 541D DF77 302B 6847 2806  D912 B3F2 D165 786D 6570

Or alternatively

Code:
gpg --verify namecoin-linux-0.13-build.assert.sig namecoin-linux-0.13-build.assert

Output is similar without the "assuming bla fasel". This shows that the information in the assert-file is signed by Jeremy Rand. The sig-file contains the signature and the assert-file contains sha256sums of the namecoin files.

Finally, find the sha256sum of the downloaded file in the assert-file

Code:
ef0fee861afe66cbf06de162ee5ee3cb88b43d281341d2f3f24ee9e9494ce5a1  namecoin-0.13.99-i686-pc-linux-gnu.tar.gz

And do something similar with the downloaded file like

Code:
sha256sum namecoin-0.13.99-i686-pc-linux-gnu.tar.gz | grep -o ef0fee861afe66cbf06de162ee5ee3cb88b43d281341d2f3f24ee9e9494ce5a1

If this returns

Code:
ef0fee861afe66cbf06de162ee5ee3cb88b43d281341d2f3f24ee9e9494ce5a1

Everythin seems fine.
 
hornetsnest
Sr. Member
****
Offline Offline

Activity: 554
Merit: 344


View Profile
May 08, 2018, 11:49:44 AM
 #1494

True though that the technology also needs to advance as it also does for other coins with active development. Standing the test of time is one thing, active development the other.
There is active development.  I've already mentioned the ConsensusJ light client.

The full client, namecoin-core follows Bitcoin development closely, the last update was 7 days ago.

The problem, for me, is still usability. It is still too difficult for the "general public" to use Namecoin. The Blockchain DNS project (browser extensions) I mentioned earlier is a big step forward as it works on two of the most popular browsers and works out-of-the-box. I think porting the Blockchain DNS extension to the remaining browsers (Safari and Edge/IE) and with a stable light client (ConsensusJ or Electrum) Namecoin can be a success.

The main reason namecoin is not heavily traded is because traders don't have a lite client to store their coins off exchanges.Same goes for regular Joe who has no interest in bit/dns and only wants a solid coin to use to buy his trash on the internet wherever a shop accepts namecoin.It all boils down to economics and the whole namecoin economy is wrong by only appealing to a niche audience.We are not all geeks but have a lot of respect for the developers of this legacy coin and many want to trade and use it for non geek stuff too.

████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████
trantute2
Hero Member
*****
Offline Offline

Activity: 728
Merit: 504



View Profile
May 09, 2018, 07:08:04 AM
 #1495

True though that the technology also needs to advance as it also does for other coins with active development. Standing the test of time is one thing, active development the other.
There is active development.  I've already mentioned the ConsensusJ light client.

The full client, namecoin-core follows Bitcoin development closely, the last update was 7 days ago.

The problem, for me, is still usability. It is still too difficult for the "general public" to use Namecoin. The Blockchain DNS project (browser extensions) I mentioned earlier is a big step forward as it works on two of the most popular browsers and works out-of-the-box. I think porting the Blockchain DNS extension to the remaining browsers (Safari and Edge/IE) and with a stable light client (ConsensusJ or Electrum) Namecoin can be a success.

The main reason namecoin is not heavily traded is because traders don't have a lite client to store their coins off exchanges.Same goes for regular Joe who has no interest in bit/dns and only wants a solid coin to use to buy his trash on the internet wherever a shop accepts namecoin.It all boils down to economics and the whole namecoin economy is wrong by only appealing to a niche audience.We are not all geeks but have a lot of respect for the developers of this legacy coin and many want to trade and use it for non geek stuff too.

Firstly, there are so many scam coins (check coinmarketcap), which have a higher market cap than Namecoin. Those projects are traded for speculative reasons, the additional benefit is limited, especially compared to Namecoin. You can't even buy something with those coins. Namecoin was once traded on kraken. They removed it. I do not know why.

Secondly, go back a few pages. There, we discussed ways to make Namecoin and the corresponding DNS more prominent. Even though our result is still limited. But I hope this will change in future.

Thirdly, I think, that there is relatively much development under way. E.g. I am looking forward to Namecoin version 0.15.99, which seems to be still in beta state (https://namecoin.org/2018/02/01/namecoin-core-0-15-99-name-tab-beta1.html).

Fourthly, the next Namecoin halving is scheduled for end of October.

Thus, it is time for this coin to shine again (imho)!
trantute2
Hero Member
*****
Offline Offline

Activity: 728
Merit: 504



View Profile
May 11, 2018, 05:20:17 AM
 #1496

Signature verification (https://bitcointalk.org/index.php?topic=6017.msg36620285#msg36620285)

I provided the wrong PGP-Key: D9D72D3A

The correct PGP-Key is: F8F7BF85

The verification worked in my case, because I had the correct key already imported!

Always check twice, what is posted in the internet!!!
CoinsInTheCan
Full Member
***
Offline Offline

Activity: 240
Merit: 101


View Profile
May 22, 2018, 05:09:01 PM
 #1497


Good news !!!

Namecoin is added to Blocknet / BlockDX (Decentralized exchange & communication protocol between many different blockchains). You can trade and build dapps for your favorite coin.  Cool   Cool   Cool

(Full launch with Litewallet and beautiful gui is July 1st)  https://bitcointalk.org/index.php?topic=829576.0
glandulaHewq
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
May 23, 2018, 07:36:19 AM
 #1498

Namecoin is one of the few tokens I have added to my portfolio for a long time. Presently ready to hold it for a long time.
ngocthach
Newbie
*
Offline Offline

Activity: 32
Merit: 0


View Profile
May 23, 2018, 10:04:20 AM
 #1499

Has anyone else got this working? There is no namecoind target in the makefile, so i built bitcoind.  My daemon is currently sitting at 0 blocks and doesn't recognize calls such as name_list and name_scan.
truxton
Hero Member
*****
Offline Offline

Activity: 772
Merit: 521



View Profile
May 23, 2018, 06:34:49 PM
 #1500

Namecoin is now ready for cross-chain dapps with the Blocknet Protocol!




Now that namecoin is compatible with the Blocknet Protocol, it can be used in cross-blockchain dapps and traded on beta Block DX!

You can read more about Blocknet, the Blocknet Protocol, and Block DX here:

https://blocknet.co

https://sites.google.com/view/blocknet/directory

To get started with trading on Block DX, follow this setup guide: https://docs.google.com/document/d/1ciwLFSXwv6CXd3QEvVW88lHXo9CSIlweYOoSbDHkies/preview

The setup is in the process of being automated/abstracted so it's much easier and streamlined to use for beginners. In addition to that, in July we are planning to release SPV support which will allow for the creation of litewallets so whole blockchains will not need to be downloaded.
Pages: « 1 ... 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 71 72 73 74 [75] 76 77 78 79 80 81 82 83 84 85 86 87 88 89 »
  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!