Will be one to watch. Would it be Scrypt-based, or an offshoot of scrypt?
Heavily scrypt based (scrypt with four different secure hash algorithms and two different stream cipher algorithms for fault tolerance and ASIC resistance in arranged in the blockchain in a randomized order) |
|
|
|
Hmmm, all of these other awesome features implemented and simplified quite nicely, but no mention of improvement to confirmation speed? I'd even be happy with a modest 50-100% speed increase just to get enough confirmations for large purchases within the first 30 minutes. Thanks for your effort, looks promising so far!
Block rate is targeted to 30 blocks per hour, or six confirmations in twelve minutes. For the first 90 days of the block chain, it will be 15 blocks per hour due to the absence of PoS and increase from there on out. This is initially a little slower than LTC, then about about the same rate. |
|
|
|
That's how I did it; be aware that when you stick the card in it tends to warp the pins with insertions in them. |
|
|
|
Link to the draft version (0.05) of the whitepaper: DownloadNotable things about this chain: - Uses a new approach to secure hashing algorithms for the hash tree of a given block that should increase FPGA/ASIC resistance - After 27 coin years it employs a system of voting to manipulate the interest rate of the block chain (users act as the central bank and regulate the rate of inflation) - Difficulty is based on the linear weighted average of the block times for the past 18 days for PoW blocks - New block reward adjustment algorithm is given that yields an 8% decrease in block reward per year - Simple PoS design (tried to strip it of as many complexities as possible) - PoW and PoS systems are designed to happily coexist, with favour slightly given to the PoW system - PoS system also intended to prevent 51% attacks - Coloured coins, e.g. for rewarding projects that you create arbitrarily - Ledger system for regular coins that allows for a lightweight version of the blockchain instead of having to download the entire blockchain Feel free to peer-review/tear it apart. I will be the first to say that I'm pretty terrible at math, so please correct any mistakes I've made. I'd love to hear why you think it's a great/terrible idea, though. Obviously I anticipate there are a lot of problems with it that I couldn't foresee, so please help me out! Official developer correspondence: dev {dot} mc2 {at} gmail {dot} com! Freenode: #MC2! |
|
|
|
The strict definition in economic terms is in regards to the money supply.
This. |
|
|
|
Bitcoin is never deflationary... in order to be deflationary coins must be removed from the supply and destroyed. The only deflationary component of PPC is the destruction of fees. The inflationary rate of Bitcoin simply decreases over time and approaches zero.
The actual amount of units of currency doesn't necessarily have to change for a currency to be deflationary. All prices going down (currency value going up) is what deflation is. Imagine a small island of 2 people. They each have 100 dollars and use it to buy stuff from each other that each can produce. Now imagine that one new person was born into this little island every month and the dollars in the island is stuck at 200. Obviously each dollar in that environment would keep gaining value (and buy more stuff the longer it is kept) - which would lead the dollar owners to not usethat cash as sparingly as they normally would. I think what you're referring to is price increases from disinflation. The Bitcoin protocol is heavily reliant on disinflation. |
|
|
|
|
Bitcoin is never deflationary... in order to be deflationary coins must be removed from the supply and destroyed. The only deflationary component of PPC is the destruction of fees. The inflationary rate of Bitcoin simply decreases over time and approaches zero.
|
|
|
|
Yes, try 12.8 drivers and set your intensity to "d" in cgminer so it mines when afk
Will do, thanks. How do I set the intensity to 'd'? Do I just type that in the box in place of the current # (ie 13)? Yep |
|
|
|
|
All hardware error, gpu is broken, increase thread concurrency or decrease intensity
|
|
|
|
|
Yes, try 12.8 drivers and set your intensity to "d" in cgminer so it mines when afk
|
|
|
|
gpu threads 2 worksize 256 thread-concurrency 8192 intensity 13 (or --thread-concurrency 8192 -g 2 -I 13 -w 256 in cgminer) Core voltage 1.087 v Memory voltage stock Core 1051 MHz Memory 1744 MHz drivers: 13.1 SDK: 2.8 722 KH/s donations always appreciated.  |
|
|
|
Windows 7 64b. I actually have it running on 2 rigs now, and the 3rd rig the only difference is the mobo which I think might be the root of my problems.
You can actually use guiminer-scrypt to generate the cgminer run command if you want to use it from a bat, just go to View --> Show Console and then click to run your cgminer on one of the other computers. It will automatically dump the command to mine with it. Additionally, if you set up a reaper tab it will generate its own copies of reaper with the settings in it as well in a folder called "reaper-yourminernamehere". |
|
|
|
LOL breaking off from BTC? It's proof of work algorithm is SHA256. Take an ASIC farm and point it at PPC network....and PPC just got fucked.
This is actually another potential danger with PPC's difficulty algorithm -- someone with a very large hash rate can buy hundreds of thousands of PPC and then hit the network hash rate very hard for a few days. Because difficultly increases AND reward decreases, the supply will be restricted severely for everyone than would be for just bitcoin. ppcoin: subsidy is cut in half every 16x multiply of difficulty Still, to achieve a 16x increase in difficulty is difficulty for most miners... except for a large one like ASICMiner. If ASICMINER, with 7 TH/s, were to buy a ton of PPC under the table from someone and then suddenly hop onto the PPC network, they could very easily completely destroy the supply of PPC for normal miners and drive up the price so long as people didn't quickly catch on to what was happening. Then they could dump their massive stock of PPC, hop off the network, and let the whole chain enter an inflationary spiral. The same could be said for BTC or LTC, but the problem is exacerbated by the manipulation of both subsidy and difficulty at the same time by miners. |
|
|
|
|
For every alt chain I've ever seen the price usually doesn't peak on BTC-e for at least a few days, usually more in the 3-14 day range.
|
|
|
|
|
Yeah, vectors doesn't do anything, but it's not really an issue. Try cgminer through guiminer-scrypt (see sig)
|
|
|
|
hmmmm I have a smalish problem: - i use ubuntu 12.10+ati 13.3+cgminer 2.11.3 video drivers on 2 rigs first rig has 6990 it only runs at speeds 610/1250, if I try to use any higher gpu clock than 610 (say 700) system will simply shutdown in 10 min or so. some of you will say that I use shitty 850W PSU from "ace" and you might be right. when it runs on 610/1250 it seems stable, no hw errors and an average of 650 kH/s, which is not much but seems fine. Here is the script I use for mining: export DISPLAY=:0
export GPU_USE_SYNC_OBJECTS=1
export GPU_MAX_ALLOC_PERCENT=100
aticonfig --od-setclocks=610,1250 --adapter=all
aticonfig --od-getclocks --adapter=all
./cgminer --scrypt --api-listen --api-network -c cgminer.conf --thread-concurrency 8192 --lookup-gap 2 --worksize 256 -I 18 -g 1 -o stratum+tcp://notroll.in:3333 -u x -p y second rig has 2x5830+5850+A4 cpu with some 6xxx type thing in it. it runs stable (for months) mining btc at 600/667 (a4) 920/600 (5830) and 910/600 (5850) with hash rates of: 28 (a4) 282 (5830) and 365 (5850). no world records there, but I'm happy mining with a stable rig that needs virtually no maintanance. LTC is a whole different matter. What ever I tried to do I would only mine for 10-15 minutes at most. When it did it was stable with no HW errors, temp was 75°C, speeds were: 25 (a4), 220 (5830) and 300 (5850) it drew no more power out of the socket as it did when it was mining btc. but after 10 minutes or so it would shut down. this rig however has high quality 1000W Corsair PSU. I Cannot get it to work stable! Here is the script export DISPLAY=:0
export GPU_USE_SYNC_OBJECTS=1
export GPU_MAX_ALLOC_PERCENT=100
aticonfig --od-setclocks=615,1200 --adapter=1
aticonfig --od-setclocks=615,1200 --adapter=2
aticonfig --od-setclocks=615,1125 --adapter=3
aticonfig --od-getclocks --adapter=all
./cgminer --scrypt --api-listen --api-network -c cgminer.conf --thread-concurrency 3072,5760,5760,5760 --lookup-gap 2 --worksize 256 -I 18 -g 1 -o stratum+tcp://notroll.in:3333 -u x -p y
it is interesting that in both cases computer would not start at the press of the power button. I had to disconnect power and reaply it and then restart the pc. this would indicate that indeed some sort of protection mechanism inside PSU triggered the shutdown. but what? Has anyone seen anything like this??? Where are these shut-downs coming from? Could this be a cpu scaling (cpu changing freq) related thing? Should I test the rig card by card? How come there is no problem mining btc even at 920/1000 on all cards? Should I reduce GPU_MAX_ALLOC_PERCENT? How about GPU_USE_SYNC_OBJECTS? p.s. third rig i tried this on uses windows, 2x5770 and 450W!!!! Corsair PSU and is able to mine ltc without a single shutdown!!! Corsair HX1000 is 2x 12v rails with 480W on each rail instead of a single rail. Try moving around your power cables, as you probably are drawing more than 480W from one of the rails. |
|
|
|
I have this same problem except it doesn't even appear in the task bar when I try to open it using 13.1 drivers. I've tried the suggestion here.
Any other thoughts on what might fix this? Been trying to get this to run all day (and since like 5 windows installs ago lol). Only thing I can get working is reaper on 12.8 drivers so far...
EDIT:
Matter of fact if someone can get this running for me on my setup via teamviewer or something (CGIminer, not reaper) successfully I'm willing to tip in LTC or BTC for your trouble. Even if all you do is walk me through successfully using CGI miner by itself!
I've never heard of this so far. What version of windows? |
|
|
|
I'm getting what I believe to be is very poor performance from GUIminer-scrypt with my Radeon 7950. I see people talking about 500-600 Khash, but I'm lucky to get above 350! I'm not sure what would be causing the problem, so let me toss out some thoughts:
1) Mining on ozcoin.net (newlc.ozco.in:9332) -- they seem to be having DDOS issues at times, or at least sluggish response times. Could that be the problem?
2) CGminer vs. Reaper -- Reaper keeps crashing and I haven't gotten it to work right yet, so I'm on CGminer.
3) Settings might be bad. Currently, I'm getting best results using Thread concurrency 8192, worksize 256, vectors 1, intensity 13, GPU threads 2. (Without the GPU threads 2, it's more like 220 Khash!)
4) Maybe a poor driver choice? I'm currently on the Catalyst 13.2 beta I think, but I was going to upgrade to 13.3. Thoughts?
Okay, that's all for now. For what it's worth, hardware is Bloomfield i7-965X at 3.6 GHz, 12GB RAM, SSD for storage. I get around 450Mhash on Bitcoin with stability using same GPU. Current GPU clocks are 965/1250. HELP!?
1) Probably, try another pool 2) Reaper should be okay, but cgminer is fine now too 3) Need aggression 20 with (high usage settings), crank your ram to 1400-1500mhz. 4) 13.2 sucks, upgrade to 13.3 or 13.1 |
|
|
|
Hey TacoTime,
First off THANK YOU for your wonderful software and excellent support!
Your efforts to make LTC mining simple have REALLY helped me.
My Q is this:
Why is my GPU load with either cgminer or Reaper bouncing all over the place?
It fluctuates from ~64% to 99%.
I'm suspecting this might be related to shy I'm getting less-than-expected hashrates from my 7970.
I'm currently getting ~500 KH/s with either cgminer or reaper, with the following settings:
Thread Con=22392
Wksize=256
V=1 (can't turn off, anything other than 1 throws errors)
Intensity=13 (anything higher glitches my desktop)
Threads=1
Stratum=No
GPU is running at 1100 Core/1800 Mem, watercooled, 60c avg temp under load.
See anything that could account for my low rates?
Once again, thanks for your hard work!
Hi, Problem is with your intensity. At 13 it will go down a lot. Glitching is normal on 13.1 drivers, crank it to 20 and let it glitch. |
|
|
|
|
Show Posts
