j-Coin information thread

[whlx]

13:00:24

getmininginfo


13:00:24

{
"blocks" : 3002,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.28103131,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 86634104,
"pooledtx" : 0,
"testnet" : false,
"Nfactor" : 4,
"N" : 32,
"powreward" : 1.00000000
}

[1715195381]

1715195381

[1715195381]

1715195381

[r3wt]

ok, j-coin sources were retrieved off of my desktop.

here ya go.

https://docs.google.com/file/d/0B5V5vln-sS3ELXpVNnY0SEltV2M/edit?usp=sharing

This is uncompilable. For example:

Main.h does not contain the hash of the genesis block (Line 48)

Code:

static const uint256 hashGenesisBlockOfficial("0x");
static const uint256 hashGenesisBlockTestNet("0x");

LoadBlockIndex(..) has a large chunk of code that's been deleted (Main.cpp, Line 2536)

Code:

    //
    // Init with genesis block
    //
    --- Block initialization should be here!
        // Start new block file
        unsigned int nFile;

Reference to non-existing methods (Main.cpp, Line 4204):

Code:

	    //thanks adam m for this fix to override nBits.
        if (pblock->IsProofOfWork())
            pblock->vtx[0].vout[0].nValue = GetProofOfWorkReward(pindexPrev->nHeight+1, nFees, pindexPrev->GetBlockHash());

bitcon-qt.rc refers to non-existing resource novacoin.ico (Line 1)

Code:

IDI_ICON1 ICON DISCARDABLE "icons/novacoin.ico"

Etc etc. There's just no way you can compile anything from this source.

lol, those minor errors are uncompilable to you? you must be super l33t.

[Bakaboy]

lol, those minor errors are uncompilable to you? you must be super l33t.

It can be fixed and "filled" to a certain extent since the genesis block hash, merkle root hash and timestamps are known and it's just a modified version of the yacoin/novacoin source. However, releasing a known good source should be the bare minimum when releasing an open source coin (imo);  to date, I've seen nothing close to that. Instead of trying to crap on people, how about releasing the actual source used to build the windows client? Makes sense? 

[r3wt]

lol, those minor errors are uncompilable to you? you must be super l33t.

It can be fixed and "filled" to a certain extent since the genesis block hash, merkle root hash and timestamps are known and it's just a modified version of the yacoin/novacoin source. However, releasing a known good source should be the bare minimum when releasing an open source coin (imo);  to date, I've seen nothing close to that. Instead of trying to crap on people, how about releasing the actual source used to build the windows client? Makes sense? 

the source i built the actual client on is bricked. i tried to remove the proof of stake or atleast modify it to take nHeight for Proof of WOrk subsidy and i fucked it all up. by taht point i realixzed i hadn't backed up the source.

[eule]

What a clusterfuck. Ever heard about a beta test?

[r3wt]

What a clusterfuck. Ever heard about a beta test?

my response is

Code:

03:48:06

getmininginfo


03:48:06

{
"blocks" : 3214,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.81839623,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 122926846,
"pooledtx" : 0,
"testnet" : false,
"Nfactor" : 5,
"N" : 64,
"powreward" : 1.00000000
}

[FoldingTime]

lol, those minor errors are uncompilable to you? you must be super l33t.

It can be fixed and "filled" to a certain extent since the genesis block hash, merkle root hash and timestamps are known and it's just a modified version of the yacoin/novacoin source. However, releasing a known good source should be the bare minimum when releasing an open source coin (imo);  to date, I've seen nothing close to that. Instead of trying to crap on people, how about releasing the actual source used to build the windows client? Makes sense? 

the source i built the actual client on is bricked. i tried to remove the proof of stake or atleast modify it to take nHeight for Proof of WOrk subsidy and i fucked it all up. by taht point i realixzed i hadn't backed up the source.

I truly appreciate your honesty here as most would not admit this.

Those that understand the gravity of your statement will stop mining and walk away and the others ... will probably keep mining in ignorance.

[paulthetafy]

Wow what a joke.  How can you possibly support a coin that you don't even have the source code for.  I was actually mining this for a while but I think I'll stop now and suggest that everyone else do the same until you sort out the source.

[hotcoldcoin]

oh well r3wt, guess your idea to not release the source code right away really backfired on you, eh?   Lesson learned, coin dead.

[r3wt]

I'll have a large order of FUD please

[paulthetafy]

I'll have a large order of FUD please

Please explain that?  Where's the FUD here?  You've released a coin for which you don't have the source code.  Fact. 

I've been mining this and would continue to do so if you can tell us what your next steps are

[r3wt]

I'll have a large order of FUD please

Please explain that?  Where's the FUD here?  You've released a coin for which you don't have the source code.  Fact.  

I've been mining this and would continue to do so if you can tell us what your next steps are

well i'm obviously trying to produce a working source for the coin. it won't compile on linux for whtever reason, and i recompiled on windows this evening with the new source, and surprise the client doesn't connect to the network. i'm gonna keep pluggin at it tomrrow when i have time. i'm going to bed tonight, its going on 430 am

[paulthetafy]

Okay cool, well it might be a good idea to keep this thread updated with progress. 

[r3wt]

Okay cool, well it might be a good idea to keep this thread updated with progress. 

have i not been here every step of the way? everytime someone posts about a build problem and i see it, i come to help. granted i haven't been here as much as i should have been, because i operate on a seriously tight schedule. i'm sure that one way or another we will get this lined out. i really need to start learning to use git. thats the lesson i'm learning here and it's a hard one.

[eule]

What a clusterfuck. Ever heard about a beta test?

my response is

Code:

03:48:06

getmininginfo


03:48:06

{
"blocks" : 3214,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.81839623,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 122926846,
"pooledtx" : 0,
"testnet" : false,
"Nfactor" : 5,
"N" : 64,
"powreward" : 1.00000000
}

Great response...  
OK your blockrate and diff adjustment works fine. My concern is, if only a few people are able to run the client, coin distribution is a joke. IMO release a coin only when everything is set up and ready for people to use.

Also:
http://devtome.com/doku.php?id=scrypt_altcoin_cloning_guide (I suppose you read it, but still...)

[r3wt]

What a clusterfuck. Ever heard about a beta test?

my response is

Code:

03:48:06

getmininginfo


03:48:06

{
"blocks" : 3214,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.81839623,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 122926846,
"pooledtx" : 0,
"testnet" : false,
"Nfactor" : 5,
"N" : 64,
"powreward" : 1.00000000
}

Great response...  
OK your blockrate and diff adjustment works fine. My concern is, if only a few people are able to run the client, coin distribution is a joke. IMO release a coin only when everything is set up and ready for people to use.

Also:
http://devtome.com/doku.php?id=scrypt_altcoin_cloning_guide (I suppose you read it, but still...)

yeah, i've read it but.... this is scrypt jane....

[eule]

yeah, i've read it but.... this is scrypt jane....

I just don't understand how you could fuck up the source (backups!) and then still release the coin instead of starting all over from mehcoin. Maybe should have held a bounty for a Windows client, we all know it's a pita to compile compared to Linux.

[r3wt]

yeah, i've read it but.... this is scrypt jane....

I just don't understand how you could fuck up the source (backups!)

you'd be surprised. i'm not just copying and pasting shit, i pour over lines and attempt to understand what each piece of the puzzle is doing and what its responsible for.

in this particular instance, i wanted to to remove proof of stake reward system but maintain the checkpointing of blocks. i failed quite miserably in doing so and was to much of a n00b to put it back. atleast i'm trying to do something new FFS. everyone else(excluding real programmers like sunny king, mikhael, free trade etc.) is doing anything more than changing a few variables and calling it innovation. at any rate, i'm gonna fix this shit as i should. another valuable(but annoying) lesson learned. ever so humbly yours,


r3wt

[eule]

Well great then, scrypt-jane without PoS sounds good (not a big fan of PoS, the rich getting richer) and feel free to hack as many coins as you want, but make sure everything works for everyone when you release it. Do a beta test first and restart the blockchain for the release, the devtome guide covers this pretty well, that's also what Neocoin does now after a failed first launch.
But now the child has dropped into the well already. 

[r3wt]

Well great then, scrypt-jane without PoS sounds good (not a big fan of PoS, the rich getting richer) and feel free to hack as many coins as you want, but make sure everything works for everyone when you release it. Do a beta test first and restart the blockchain for the release, the devtome guide covers this pretty well, that's also what Neocoin does now after a failed first launch.
But now the child has dropped into the well already.  

lol, i like you eule, you seem like a quite reasonable person. you stated your concerns and made your points concisely without resorting to slanted arguments  such as the qouted instance below, and i have respect for that. slinging mud and fud solves nothing.

"Oh you didn't release a source, your coin is now dead blah blah blah i'm a troll"