 Show Posts
|
|
Pages: « 1 [2]
|
Could we have some details on the decided changes?
This may sound like tech Jargon but I'll do my best to explain: As far as I know, the only thing being changed that requires the hard fork is the time allowed for the search interval (hashdrift) and also the timedrift. This is basically a security update related to the possible vulnerability of a time-warp attack. Basically, all that is happening is that the time allowed for the hashdrift and the timedrift are being reduced. The hashdrift is being reduced to 15 seconds and the timedrift is being reduced to 30 seconds which is in line with mintcoin's 30 second block target. A timedrift that is further out in time than the block target presents a vulnerability. The vulnerability is a potential to trick the Mintcoin network into ever decreasing difficulty. This hard fork will make this impossible. The hashdrift (timestamp search interval) is being lowered to help prevent a surge in orphan blocks, as it is better to have the time of the hashdrift below the time of the timedrift. The hashdrift (timestamp search interval) helps the network know what time it is so that it can basically keep the ledger going on a continual time that everyone agrees on. Specifically: The hashdrift (timestamp search interval) is being reduced to 15 seconds. The timedrift is being reduced to 30 seconds. As far as Supasonic's changes, these are just some wallet GUI optimizations that don't require the hard fork, but are going to be included in it anyway, just to make the wallet more user-friendly. I hope that helps explain. If anyone knows better, or wants to add to this, please do.  Thanks that makes sense I think , I got a couple of things wrong on how I thought my p2p protocol worked (it actually uses the average time calculated between connected clients and removed outliers above a certain limit but not looked at it for like 14 months. it also had a different purpose than a coin and was designed more like bittorrent as a distributed database. Building 50 nodes in an L(1) configuration Vid on 1 computer using TCP average of 14 connections per client, 320 nodes in a least redundancy configuration= vid I'm sure there are some major flaws in security but I'm learning) (in case anyone is interested) |
|
|
|
|
Could we have some details on the decided changes?
|
|
|
|
|
I wrote a small (amatuer) p2p algorithm, just as a test. And I've only half read the things posted lately. But in my little P2p thing I added a constraint on the time per client (assume your time is correct and only accept times that are within a certain range). As I had control over all the computers I tested it on I set it fairly low (1 min). But shouldn't it result in a consensus on the network. I'm not sure I really understand your issue unless you are suggesting multiple clients that all offset by 1 min in my example and enough clients to override the whole system. Dont mintcoin clients have the same priority as far as time is concerned?
|
|
|
|
I have an issue with the wallet (1.17) on the computer I've been running it on for a year (windows 7 64bit), the splash screen loads up, it loads the block index etc. The UI then pops up and sits there in a Not responding state. This happened after the computer lost power while the wallet was open and unlocked for minting.
The debug.log isnt showing any errors, the daemon seems to be running fine in the background behind the UI (I can see it updating the blockchain correctly).
I've found a way to get it running by simply copying the data to another computer (also windows 7 64bit) and running an identical copy, it runs fine then. Which leads me to think it's likely a temporary file or something lying around on the original computer that's not in the data folder or the mintcoin program folder.
You need to download and run the whitecoin wallet, then close it and open your mint wallet and it will be ok, I know it seems odd, but it works! When you do this, do you need to let the Whitecoin wallet sync completely before closing it out, or, will just running it for a bit, and then exiting work? I don't currently have any problems, just curiosity. You just open it for like 15 seconds. Then go back to Mintcoin and it should work. I believe any Mintcoin clone coins can do the trick too. Fixed it, I deleted the BitcoinURI file in the "C:\ProgramData\boost_interprocess\Select LastBootUpTime from Win32_OperatingSystem" folder Okay great. How did you figure that out? I used Process Explorer to view the handles used by mintcoin, ignoring dlls, files in the mintcoin folder and registry entries that left just one file Tested it on a fresh datadir just to be sure. I guess whitecoin etc. are using a more recent version of the boost library. |
|
|
|
I have an issue with the wallet (1.17) on the computer I've been running it on for a year (windows 7 64bit), the splash screen loads up, it loads the block index etc. The UI then pops up and sits there in a Not responding state. This happened after the computer lost power while the wallet was open and unlocked for minting.
The debug.log isnt showing any errors, the daemon seems to be running fine in the background behind the UI (I can see it updating the blockchain correctly).
I've found a way to get it running by simply copying the data to another computer (also windows 7 64bit) and running an identical copy, it runs fine then. Which leads me to think it's likely a temporary file or something lying around on the original computer that's not in the data folder or the mintcoin program folder.
You need to download and run the whitecoin wallet, then close it and open your mint wallet and it will be ok, I know it seems odd, but it works! When you do this, do you need to let the Whitecoin wallet sync completely before closing it out, or, will just running it for a bit, and then exiting work? I don't currently have any problems, just curiosity. You just open it for like 15 seconds. Then go back to Mintcoin and it should work. I believe any Mintcoin clone coins can do the trick too. Fixed it, I deleted the BitcoinURI file in the "C:\ProgramData\boost_interprocess\Select LastBootUpTime from Win32_OperatingSystem" folder |
|
|
|
|
I have an issue with the wallet (1.17) on the computer I've been running it on for a year (windows 7 64bit), the splash screen loads up, it loads the block index etc. The UI then pops up and sits there in a Not responding state. This happened after the computer lost power while the wallet was open and unlocked for minting.
The debug.log isnt showing any errors, the daemon seems to be running fine in the background behind the UI (I can see it updating the blockchain correctly).
I've found a way to get it running by simply copying the data to another computer (also windows 7 64bit) and running an identical copy, it runs fine then. Which leads me to think it's likely a temporary file or something lying around on the original computer that's not in the data folder or the mintcoin program folder.
|
|
|
|
I don't suppose you could reduce the start minting after Sync level value, maybe 10k blocks or so. perhaps even make it based on the weight value.  |
|
|
|
|
I have some android experience (programming), little P2P stuff. If you want a beta tester then I'm up for it (just send me a PM) - (prepared to lose some mint to test it)
|
|
|
|
|
I've got some coins in a wallet and its all working fine, minting etc. But I was wondering 2 things.
1) when minting does it have the ability to combine multiple inputs for one stake? (don't think I've seen this happen so far) and
2) when the stake is returned its halved and becomes 2 inputs, is there a minimum level that this will happen down to? Because I obviously don't want to end up with billions of inputs at 0.00000001 mint and yes I know I can recombine inputs manually by sending them to myself, just wondering if there's a limit in place.
|
|
|
|
|
Not throwing more miners at it in 2012, I really wanted to, but something convinced me otherwise.
|
|
|
|
|
