Topic: âš’[CGA] Cryptographic Anomaly - The Elusive Coinâš’ - page 120. (Read 226291 times)

Because it came up in the last few posts:
I'll offer an escrow service for CGA trades. I think I built enough trust in the CGA community to provide this kind of service successfully. Sawedoff gave his blessing already, I just want to ask you to put my offer in your opening post. My fee is 0.1 %. Thank you!

If there are any trades you might consider, drop me a line and I'll arrange everything.

Back to the discussion about how the coin is developing: Get a plan first (as I already wrote like 1080 times before), build a realistic timeline and then go to work. I'd be happy to help you with all kinds of planing, that wouldn't be the first software product I'd consulting. Besides that I agree totally to the posting containing the topic of leadership and decision-maker: There HAS to be ONE policy maker, MANY will not work properly. Sawedoff, for god's sake, grab your guts and tell us what to do

I already made a sumit a few days ago, you can use this todo list to build up a priorized (or priorised?) task board, assign tasks to people you trust and you think they'll get the job done IN TIME AND QUALITY.

This is not about tasks, this is about how to organize the community and the contributers. First: Build up a process; Second: Define the tasks; Third: Do your work.

I agree completely and that is why I called them "milestones" and not a plan.  Perhaps I wasn't wholly crystal clear, but what I meant was, something like:

A. stabilise ecosystem - during February
B. re-fresh wallet (perhaps with key features x and y), v1.1.1.N - late Feb/early March
C. target exchange listing March
D. etc.

So these would form a provisional timeline and you would nail down each item with exact dates as you got closer.

Also I don't think we should over-engineer it - it is not about providing a detailed plan,  rather to show here is a coin with a real vision.

UP +++

I agree with this in principle, but with regard to setting milestones, they must be careful not to make announcements unless they absolutely can fulfill them. You can't announce a time for a mandatory update and still be scrambling around trying to get a Window client finished, then unleash directly from the compiler to the userbase without any real testing. That is a recipe for absolute disaster.

Discuss plans and be open about things, but be careful about commitments. IOW, underpromise and overdeliver.


And the bounty shouldn't be for a windows client, the bounty should be for a VM with everything in place and ready to compile so the devs can focus on actual code instead of chasing libraries and header files.

I've worked on the Windows client and I know it's hard work. It throws such an incomprehensible amount of arcane WTF crap in your face it's almost comical... Do I have a thousand errors, or do i have one error it's telling me about a thousand times?.... Ahhh, good times. Good times.

can you please keep your ideas -like mining more coin before more people come - to yourself.
Go make a coin and mine yourself. So you can have them all!!!

Of course a dev. can decide for the coin but there are borders he can't go without community approval.
If a dev. has ideas like hardforking coins general parameters, refusing exchanges ext. he may keep them for himself.
He need to ask to community before doing something like that or he can find himself alone. (and without coin if coin is trading at an exchange- if it has $ value- and we're saying it community takeover).




You and rfe3 have responsibility for this.
Any of you want more issues like this to happen?

that dude wanted to buy my CGA too...
the differance between chickenliver503 and me was; i wasn't in such a hurry to send first or trade without a trustable escrow.

 s4w3d0ff: we're talking too much about 'dev' between us, sorry. I can feel you're a great guy.
My two cents are; if there are some posts- ideas- against normal process, please use 'statistics' ,. Math will never lie.

Regarding getting the coin on an exchange and the overall strategy, although I was initially very supportive of getting on an exchange after some thought I have reconsidered.

I think what we need first is a clear vision for CGA, and what is being planned.

My first thoughts:

1. Clear up the current challenges around forking / and the nodes and ensure we have a really stable ecosystem to support the coin, this is crucial
2. Ensure that any future releases/updates are done only when all compiled wallets are available
3. Try to move to a position where it is less important which version of the wallet is being used - I think there is a clear difference between the infrastructure (pools, nodes, etc.) and ordinary end users; when the number of users gets large this will become more and more challenging if not addressed
4. If possible, consider reducing the total number of coins that *could* be generated.  I will confess, I am in two minds about this: on the one hand I like the idea of completely future proofing CGA, and I realise that the theoretical maximum is just that and the real number will likely be far lower; but on the other hand I think a max number in the billions sends the wrong message for a "rare" coin. 
5. Progress the branding - we have the logo contest (though in truth I see little wrong with the current logo); it would be good to have a currency symbol as well.
6. Communicate this clearly, including an indicative timeline when we think key milestones will be reached (like new releases, getting on an exchange, etc.)  - the website will need to be updated
7. Get more people involved, esp. in dev

I'm happy to do what I can (subject to other commitments like work and family ... ). Although I am definitely a techie I'm not a dev and my skills are more in organisation and planning.

It seems that around 6:30 PST, is when the chain / fork happened. Checking debug log for more information.

MPOS:cga.altcoinpool.org/
The pool is not money, who knows why??

You may of been on the wrong chain. We have come to believe that someone is solo mining on the wrong chain with a lot of hashing power. This my be causing the forks. If you are solo mining please delete all the "addnode"s from your config file and restart your wallet so you solo mine on the correct chain.

I guess you were on a fork, now you are on the right chain. Sorry for your lost coins I'd suggest to mine on one of the p2pools, they are very stable and are always on the right chain.

did that error,seems to be gone now gone.

I was at work for a few hours and came home and it said i had found 65 blocks...

"version" : 1010102,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : xxxx,
"blocks" : 11819,
"timeoffset" : -9,
"connections" : 8,
"proxy" : "",
"difficulty" : 0.58691038,
"testnet" : false,
"keypoololdest" : 1391301918,
"keypoolsize" : 48,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""
}

but the balance is incorrect

We'd need your "getinfo".

You could also try: Stop your wallet, delete blockchain and peers.dat, start your wallet and look if you get the same balance as before.

How can i tell if my personal wallet forked? and that im solo'ing on the right one?

I check getpeerinfo

[
{
"addr" : "184.154.116.146:13931",
"services" : "00000003",
"lastsend" : 1391930587,
"lastrecv" : 1391930587,
"bytessent" : 18592,
"bytesrecv" : 146006,
"blocksrequested" : 0,
"conntime" : 1391930575,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 11797,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "50.147.39.37:13931",
"services" : "00000003",
"lastsend" : 1391930577,
"lastrecv" : 1391930579,
"bytessent" : 229,
"bytesrecv" : 8397,
"blocksrequested" : 0,
"conntime" : 1391930575,
"version" : 70002,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : false,
"startingheight" : 8211,
"banscore" : 0
},
{
"addr" : "71.105.130.10:13931",
"services" : "00000003",
"lastsend" : 1391930596,
"lastrecv" : 1391930592,
"bytessent" : 19207,
"bytesrecv" : 175911,
"blocksrequested" : 0,
"conntime" : 1391930575,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 11797,
"banscore" : 0
},
{
"addr" : "149.210.168.71:13931",
"services" : "00000003",
"lastsend" : 1391930582,
"lastrecv" : 1391930587,
"bytessent" : 174,
"bytesrecv" : 7106,
"blocksrequested" : 0,
"conntime" : 1391930581,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 11797,
"banscore" : 0
},
{
"addr" : "162.243.115.27:13931",
"services" : "00000003",
"lastsend" : 1391930585,
"lastrecv" : 1391930583,
"bytessent" : 229,
"bytesrecv" : 7075,
"blocksrequested" : 0,
"conntime" : 1391930582,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 11769,
"banscore" : 0
},
{
"addr" : "23.16.241.50:13931",
"services" : "00000000",
"lastsend" : 1391930583,
"lastrecv" : 0,
"bytessent" : 126,
"bytesrecv" : 0,
"blocksrequested" : 0,
"conntime" : 1391930583,
"version" : 0,
"subver" : "",
"inbound" : false,
"startingheight" : -1,
"banscore" : 0
}
]

im running wallet 1.1.1.2

I agree with you, after trying for hours (s4w3d0ff can attest to this) to cross-compile the qt wallet under Linux.

the windows wallet is runing the latest github v1.1.1.2

I tried it, I'm a technical person - and I failed. Building a windows wallet is like mixing beer and coke. It's just not right.

Is it possible to create a windows wallet with QT creator? I'm not a technical person and I'm just trying few tutorials I found online.

switch to anomalypool.com, it has a higher speed rate than inceptioncraft.
inceptioncraft has  2.48 mh/s when anomalypool has 48 mh/s and founding most of the blocks.

Seems like we need a compiled windows wallet of the latest github source.

Done it already. I'm using Win 7 x64.