Topic: [ANN][EC]▲ Eclipse ▲ Ring Signatures | Anonymous | TOR | Stealth Addresses - page 12. (Read 29638 times)

Is there a block explorer yet? If not, I'd suggest making that next on your list of things to do.

Sometimes communication is easier on IRC vs the forums here at bitcointalk, so I registered and created the channel if anyone is interested in joining/participating. #eclipsecoin on freenode.

https://kiwiirc.com/client/irc.freenode.net/#eclipsecoin

NICE!!

That is great looking work. 

I'm shocked at the reveal after the iffy launch.

We are very interested. Obviously, we can't post pictures yet, but we are currently discussing the look.

A comment from one of the devs: "i like it, only thing that is an issue with me is that the planet in the center (or whatever it is) makes me think of a negative connotation (like no smoking or whatever)....i mean, if it were more planet-y, i like it".


Also, it is "eclipse crypto", not "coin" because there are technically more than one "coin" here.

Is it possible to give the "e" less of a negative connotation?

We are also discussing a bounty. We know this is work.

Thanks for the informative post Eclipse.  Tweeted it out because it seems to be a significant addition to this coin. 

The Eclipse launch was noted on our podcast on saturday.  If you are interested in hearing the part about eclipse you can check it out @ http://thecryptoworld.org/innagural-blockchain-dynamics-radio-show the mention of Eclipse is @ 49:04:00 .  It is brief but we were going through many coins and could only mention them for a minute.  I will be sure to describe your post with this update about Eclipse on our next show and if you have any more information we could pass on, or if you yourself would like to speak on the show, please let me know.

Best of luck on your project

https://bitcointalksearch.org/topic/blockchain-dynamics-show-thread-1379730

To hell with it, here comes the cat out of the bag.

Eclipse is the first truly cryptographically anonymous coin based on the bitcoin protocol.

It is forked from shadowcash, which was completely de-anoned. See here: https://shnoe.wordpress.com/2016/02/11/de-anonymizing-shadowcash-and-oz-coin/

You will see from Shen Noether's write-up that they used a cryptographically insecure hashToEC function.

Here, we replaced their hashToEC with a cryptographically secure variant. Right now shadowcash is still not anonymous. Eclipse is anonymous.

The writeup linked above describes how the shadowcash hashToEC is broken, so I won't go into it here.

We use what is known as "try-and-increment hashing to an elliptic curve". It is a simple algorithm that is used in several cryptosystems. Key image with our algo goes like this:

1. take a scalar hash (e.g. SHA256d) of the public key (k) and map it to x on the secp256k1 discrete field
2. determine whether this x is a quadratic residue of secp256k1
3. if x is not a quadratic residue, set x = x+1 and go to 2
4. else x is a quadratic residue so keep the point x, y, where y is the positive solution to x for secp256k1, let's call this point p
5. multiply the point p = (x,y) by the scalar representing the private key x, such that key image I = xp

You can verify this is our algo by looking at secp256k1_hash_to_ec_xy_bytes() in our source tree at src/secp256k1/secp256k1/src/secp256k1.c. Rather than re-invent the wheel, we used bitcoin's secp256k1 library to determine the suitability of x and to find it's root to map point x,y.

Happy mining!


Edit:

I forgot to add that anyone who investigates may come across a caveat about try-and-increment where it is subject to "timing attack". Timing attack is absolutely not relevant to ring signatures though, because everyone already knows what a timing attack might reveal: the curve, the input k, and the scalar hash algorithm used. Going back to the original cryptonote white paper, the private key x is protected by discrete logarithm hardness.

Edit:

We have a whitepaper coming that goes into more detail and summarizes Shen's work.

i'm happy with your pool

what is the purpose of this coin?

Actually didn't take too much tweaking on my end. ./autogen.sh didn't like the += on lines 117 and 118 of secp256k1/Makefile.am so I had to correct that. export CC_FOR_BUILD=gcc, and manually install gmp in /usr/local. I think that was it. Took a while for me to figure out those, and your initial instructions about gmp were the last of what i needed to get it compiled.

Hope everyone has been happy with the mining so far at superninjapool.tk 

A few on the team have been mining on your pool since you opened it up and superninjapool . tk has been rock solid.

One thing: if you tweaked the source to remove the secp256k1 dependency in sigringu.cpp, please rebuild with the latest commit.

Removing the dependency will, when validating certain kinds of sending transactions, result in an uninitialized array with essentially random values. This means your node will reject some valid transactions.

We guess you probably fixed it by modifying the autoconf generated configure file, but if you changed the source you might run into the problem described.

Thanks again for your pool services!

Ofcourse mate suprnova.cc most reliable pool out there.

Thank you.  Shot you a PM as well.

Looks like ec.suprnova.cc is up and running, okay to mine there?

Eclipse Twitter Promotion!

In order to star to bring awareness to Eclipse, we are going to be making a large push on Twitter and rewarding our followers who participate!

The first promotion will reward users with 15 EC simply for following twitter.com/EclipseCrypto and providing your EC address.

Step 1: Sign on to Twitter and follow twitter.com/EclipseCrypto
Step 2: Fill out this Google form to provide us your address so we can track activity without annoying you every time: http://goo. gl/forms/ga2gcFsUsO (copy/remove space)

Here are the rules:
1: Obviously you've gotta be a follower
2: You have to have at least 50 REAL followers (we'll verify on TwitterAudit)
3: Participate and earn EC

That's it.  Stay tuned to the thread and we'll have regular promotions to earn additional EC!

Are you sure that secp256k1 finished building? You can't comment out that include.

Your error looks like secp256k1 didn't finish building.

Did you try a fresh pull and build with our make file?

sorry , my fault with the .conf file .

Too sleepy rightnow and Eyes to lazy


all good


 "version" : "v1.0.0.0-g",
    "mode" : "full",
    "state" : "Full Node",
    "protocolversion" : 60017,
    "walletversion" : 10500,
    "balance" : 0.00000000,
    "eclipsebalance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "reserve" : 0.00000000,
    "blocks" : 802,
    "timeoffset" : -1,
    "moneysupply" : 1313221.25350400,
    "connections" : 10,
    "datareceived" : "426.91 KB",
    "datasent" : "49.62 KB",
    "proxy" : "",
    "ip" : "eedngwl7r7p3aqc5.onion",
    "difficulty" : {
        "proof-of-work" : 9143104.18414356,
        "proof-of-stake" : 182635.91124866
    },
    "testnet" : false,
    "keypoolsize" : 0,
    "paytxfee" : 0.00020000,
    "mininput" : 0.00000000,
    "errors" : ""

dev without  #include "eclipse.h" in init.h the error is solved is required the #include "eclipse.h" ?

i need multiple ports for different coins

why ? i use 3333

it does not allow to change RPC Port with my eclipsecrypto.conf