Pages:
Author

Topic: deleted - page 37. (Read 68074 times)

hero member
Activity: 635
Merit: 500
September 21, 2014, 12:30:48 PM
#10
New wallet don't sync. Any nodes?
hero member
Activity: 686
Merit: 500
September 21, 2014, 08:20:48 AM
#9
The wallet wont sync beyond block 172800. You must upgrade the wallet in order to do so. That prevents a blockchain forking in case of incompatible wallet versions. Simple, but very effective.

Yes, I'll upload the source to github. I've an account for that.

There are no pools yet. We need one.

Why didn't people think of that earlier?

If this's added to Bitcoin, it'll reach heights of scalability.
member
Activity: 107
Merit: 10
September 19, 2014, 04:15:15 PM
#8
Inflation 5%? why?
member
Activity: 69
Merit: 10
September 19, 2014, 01:29:38 PM
#7
member
Activity: 116
Merit: 10
September 19, 2014, 12:37:55 PM
#6
Your use of the word 'cause' gives me much lols. Add some 'aint' and 'reckon' in there too, Alabama style!

ASIC proof
For the first time in any cryptocurrency, we guarantee you this coin will remain ASIC proof cause of it's scalability.

Not sure how this is a first, unless you mean automated hardforking. Plenty of other coins guarantee this.
legendary
Activity: 1176
Merit: 1015
September 19, 2014, 12:09:22 PM
#5
First of all, you need to add all your source code to github, I'm not downloading anything from onedrive.

Next, do you have a white paper describing this functionality? What exactly is happening when the block number 172800 arrives? I guess the user must download a new wallet?
member
Activity: 69
Merit: 10
September 19, 2014, 12:06:33 PM
#4
blocks 58099  lol
full member
Activity: 205
Merit: 100
September 19, 2014, 12:05:15 PM
#3
pools?
member
Activity: 69
Merit: 10
September 19, 2014, 12:02:38 PM
#2
algo?
sr. member
Activity: 420
Merit: 250
September 19, 2014, 12:01:27 PM
#1
deleted
Pages:
Jump to: