Pages:
Author

Topic: [ANN] Guncoin(GUN) - New GUN Core V2.0 Released - Masternodes are HERE! - page 48. (Read 187710 times)

sr. member
Activity: 539
Merit: 255
Bug report in wallet v 1.3.

I've been running 1.3 on one computer for a while and it's been fine.  So I upgraded all my wallets this am, and the one on my mining rig (running Win7 x64) crashed after giving this error. (the forum won't let me attach screen cap)


Code:
MinGW Runtime Assertion

Assertion failed!

Program: c:\(blabla)\guncoin-qt.exe
File: checkpointsync.cpp, Line 184

Expression: mapBlockIndex.count(hashSyncCheckpoint)



As a side note, the wallet crashes on every start with that same error.

And when reverting to the old 1.2 beta, the db has to be re-indexed, that will be hours..

That is very odd - not seeing anything like that on my wallets.  what type of machine and system is it running on?


Yeah, very odd indeed..

As mentioned, it's a win7 x64 'popsicle' mining rig (AMD 8350 GPU/mobo/16gig ram screwed to a wood shelf that also hangs my GPU's), that's dedicated to mining, and occasionally bit torrenting.  Everything else that I've put the wallet on is fine with it.  

The interesting part, is that it crashed on the checkpoint part, when the checkpoints aren't activated yet.
sr. member
Activity: 781
Merit: 276
Im trying to update to v1.3 wallet on the mac and getting this error:



Any ideas? Im on Sierra 10.12.6. The previous version (v1.2) was opening fine, but had the 1111111 in the address problem.

EDIT: Actually no... everything looks fine. I deleted everything except the wallet.dat and reopened. Its working and syncing. It was showing that error when the old files were still in the directory Smiley

Actually, bushstar had a post a few pages back that told about this on some machines.  You can simply change online in your config file and it solves the problem.  I updated 3 wallets and got the same error on one.  Changed the line and the problem went away.  If you deleted everything, and reloaded, you probably have no issues.
member
Activity: 91
Merit: 10
Im trying to update to v1.3 wallet on the mac and getting this error:



Any ideas? Im on Sierra 10.12.6. The previous version (v1.2) was opening fine, but had the 1111111 in the address problem.

EDIT: Actually no... everything looks fine. I deleted everything except the wallet.dat and reopened. Its working and syncing. It was showing that error when the old files were still in the directory Smiley
sr. member
Activity: 781
Merit: 276
mining it. I'm from Texas.

Excellent - thanks for joining the group!  If you are the new one on TheBlocksFactory - welcome there too.
full member
Activity: 287
Merit: 100
mining it. I'm from Texas.
sr. member
Activity: 781
Merit: 276
All in for future privacy features....definitely a plus when it comes to digital currency.

Also....great job on getting soooooo close to a million dollar marketcap, maybe we'll be there or even past once this posts.

I believe that is a huge milestone.


Edit: just checked, we're there... over a million dollar marketcap!!!

Yes, we actually broke the $1MIL mark a few minutes ago.  Prices fluctuating around 29 sats right now with volume over 0.8BTC on volume over 3MIL GUN - all of those are record highs for GUN. I guess traders like the direction we are heading.
sr. member
Activity: 318
Merit: 253
All in for future privacy features....definitely a plus when it comes to digital currency.

Also....great job on getting soooooo close to a million dollar marketcap, maybe we'll be there or even past once this posts.

I believe that is a huge milestone.


Edit: just checked, we're there... over a million dollar marketcap!!!
sr. member
Activity: 781
Merit: 276


I can't really offer any technical insight since that's way beyond my paygrade so to speak.  I can attest that anything with the word "Masternodes" in it is insanely popular right now and Privacy aspects are looking to be pretty popular in 2018 too.

Understand and agree.  All of these are good ideas for valid consideration in a future build once we have V1.4 rolled out and completed and a working mobile wallet.  At that point, we can customize the coin a little more to our unique desires.  Keep in mind, some of these things may conflict with other or have to be rolled into the coin in serial fashion rather that all at once.  But I like the ideas so far.
sr. member
Activity: 1246
Merit: 274
No need to mention the alt, but this is what I think they mean:

1. Zerocoin. There is a "minting" option in the wallet, that turns your GUN into zGUN... Using zero knowledge proofs that you own a certain amount of zGUN, these are all mixed into a pool of other zGUN, and when it comes time to spend it, you "withdraw" to a regular GUN address. The zGUNs have fixed denominations, much like "normal" fiat currencies, such as 1, 2, 5, 10, 20, 50, 100, 500, 1000.

That GUN in the new address will seem to have gotten GUN out of thin air, or out of the zGUN cloud or whatever it is. People will see it came from the pool, but can't prove where it originally came from. Everyone else participating in the zerocoin protocol get the same thing. There may be a transaction fee or something.

2. Masternodes. They seem to be getting popular these days, the grand daddy of them all is DASH. There are like 70 of them now. You need to somehow strike a balance between the collateral required for a node and the overall coin supply. These masternodes usually perform other functions aside from hosting a full node, such as faster transactions (that cost more), and a variation of coin obfuscation, or processing the zerocoin, and maybe even a budget system that is voted by all other masternodes. For their service, these nodes earn a percentage of the coins mined by miners, something like a 45% / 45% / 10% split between miner, node, and the budget system.

Masternodes lock up a percentage of the coins in circulation; they can not be spent as long as the nodes are operating. The result is pressure on the buy side for other people who want to run a node too, increasing the price of the coin in the process.

The number of nodes will keep increasing either until the coin supply runs out, or the ROI for running a node approaches zero percent. Dash supposedly has thousands of nodes, locking up a quarter of the total supply, costs $1m in collateral to run one, and owners earn about 20% per year on it.

Both of these would require either a hard fork, or an entirely new coin. If the same address format is retained, then a swap may be optional and people can just claim their coins using the private keys they already possess.


There are other systems out there too, such as DPoS (Delegated Proof of Stake). Those run about a hundred high powered servers, 20 that act as regular super nodes + 1 out of the other hundred chosen randomly. Each one is voted in by people who have a stake (other coin holders). It's decentralized by the stake holders, but the delegates are intentionally limited to 21, or 53, or some other odd number.

I can't give you more info as that's my understanding of it at the moment. Someone else needs to chime in, or a search should turn up something.

Very good - all interesting things to consider.  Thanks for the details!



I can't really offer any technical insight since that's way beyond my paygrade so to speak.  I can attest that anything with the word "Masternodes" in it is insanely popular right now and Privacy aspects are looking to be pretty popular in 2018 too.
sr. member
Activity: 781
Merit: 276
With the release of GUN V1.3, a record BTC price, record GUN trading volume and higher GUN prices, I am please to report that GUN is nearing a $1 MIL market cap for the first time.  The GUN Team thanks yo so much for your continued support!
sr. member
Activity: 781
Merit: 276
Bug report in wallet v 1.3.

I've been running 1.3 on one computer for a while and it's been fine.  So I upgraded all my wallets this am, and the one on my mining rig (running Win7 x64) crashed after giving this error. (the forum won't let me attach screen cap)


Code:
MinGW Runtime Assertion

Assertion failed!

Program: c:\(blabla)\guncoin-qt.exe
File: checkpointsync.cpp, Line 184

Expression: mapBlockIndex.count(hashSyncCheckpoint)



As a side note, the wallet crashes on every start with that same error.

And when reverting to the old 1.2 beta, the db has to be re-indexed, that will be hours..

That is very odd - not seeing anything like that on my wallets.  what type of machine and system is it running on?
sr. member
Activity: 539
Merit: 255
Bug report in wallet v 1.3.

I've been running 1.3 on one computer for a while and it's been fine.  So I upgraded all my wallets this am, and the one on my mining rig (running Win7 x64) crashed after giving this error. (the forum won't let me attach screen cap)


Code:
MinGW Runtime Assertion

Assertion failed!

Program: c:\(blabla)\guncoin-qt.exe
File: checkpointsync.cpp, Line 184

Expression: mapBlockIndex.count(hashSyncCheckpoint)



As a side note, the wallet crashes on every start with that same error.

And when reverting to the old 1.2 beta, the db has to be re-indexed, that will be hours..
sr. member
Activity: 539
Merit: 255
Bug report in wallet v 1.3.

I've been running 1.3 on one computer for a while and it's been fine.  So I upgraded all my wallets this am, and the one on my mining rig (running Win7 x64) crashed after giving this error. (the forum won't let me attach screen cap)


Code:
MinGW Runtime Assertion

Assertion failed!

Program: c:\(blabla)\guncoin-qt.exe
File: checkpointsync.cpp, Line 184

Expression: mapBlockIndex.count(hashSyncCheckpoint)

sr. member
Activity: 781
Merit: 276
No need to mention the alt, but this is what I think they mean:

1. Zerocoin. There is a "minting" option in the wallet, that turns your GUN into zGUN... Using zero knowledge proofs that you own a certain amount of zGUN, these are all mixed into a pool of other zGUN, and when it comes time to spend it, you "withdraw" to a regular GUN address. The zGUNs have fixed denominations, much like "normal" fiat currencies, such as 1, 2, 5, 10, 20, 50, 100, 500, 1000.

That GUN in the new address will seem to have gotten GUN out of thin air, or out of the zGUN cloud or whatever it is. People will see it came from the pool, but can't prove where it originally came from. Everyone else participating in the zerocoin protocol get the same thing. There may be a transaction fee or something.

2. Masternodes. They seem to be getting popular these days, the grand daddy of them all is DASH. There are like 70 of them now. You need to somehow strike a balance between the collateral required for a node and the overall coin supply. These masternodes usually perform other functions aside from hosting a full node, such as faster transactions (that cost more), and a variation of coin obfuscation, or processing the zerocoin, and maybe even a budget system that is voted by all other masternodes. For their service, these nodes earn a percentage of the coins mined by miners, something like a 45% / 45% / 10% split between miner, node, and the budget system.

Masternodes lock up a percentage of the coins in circulation; they can not be spent as long as the nodes are operating. The result is pressure on the buy side for other people who want to run a node too, increasing the price of the coin in the process.

The number of nodes will keep increasing either until the coin supply runs out, or the ROI for running a node approaches zero percent. Dash supposedly has thousands of nodes, locking up a quarter of the total supply, costs $1m in collateral to run one, and owners earn about 20% per year on it.

Both of these would require either a hard fork, or an entirely new coin. If the same address format is retained, then a swap may be optional and people can just claim their coins using the private keys they already possess.


There are other systems out there too, such as DPoS (Delegated Proof of Stake). Those run about a hundred high powered servers, 20 that act as regular super nodes + 1 out of the other hundred chosen randomly. Each one is voted in by people who have a stake (other coin holders). It's decentralized by the stake holders, but the delegates are intentionally limited to 21, or 53, or some other odd number.

I can't give you more info as that's my understanding of it at the moment. Someone else needs to chime in, or a search should turn up something.

Very good - all interesting things to consider.  Thanks for the details!

legendary
Activity: 3416
Merit: 1912
The Concierge of Crypto
No need to mention the alt, but this is what I think they mean:

1. Zerocoin. There is a "minting" option in the wallet, that turns your GUN into zGUN... Using zero knowledge proofs that you own a certain amount of zGUN, these are all mixed into a pool of other zGUN, and when it comes time to spend it, you "withdraw" to a regular GUN address. The zGUNs have fixed denominations, much like "normal" fiat currencies, such as 1, 2, 5, 10, 20, 50, 100, 500, 1000.

That GUN in the new address will seem to have gotten GUN out of thin air, or out of the zGUN cloud or whatever it is. People will see it came from the pool, but can't prove where it originally came from. Everyone else participating in the zerocoin protocol get the same thing. There may be a transaction fee or something.

2. Masternodes. They seem to be getting popular these days, the grand daddy of them all is DASH. There are like 70 of them now. You need to somehow strike a balance between the collateral required for a node and the overall coin supply. These masternodes usually perform other functions aside from hosting a full node, such as faster transactions (that cost more), and a variation of coin obfuscation, or processing the zerocoin, and maybe even a budget system that is voted by all other masternodes. For their service, these nodes earn a percentage of the coins mined by miners, something like a 45% / 45% / 10% split between miner, node, and the budget system.

Masternodes lock up a percentage of the coins in circulation; they can not be spent as long as the nodes are operating. The result is pressure on the buy side for other people who want to run a node too, increasing the price of the coin in the process.

The number of nodes will keep increasing either until the coin supply runs out, or the ROI for running a node approaches zero percent. Dash supposedly has thousands of nodes, locking up a quarter of the total supply, costs $1m in collateral to run one, and owners earn about 20% per year on it.

Both of these would require either a hard fork, or an entirely new coin. If the same address format is retained, then a swap may be optional and people can just claim their coins using the private keys they already possess.


There are other systems out there too, such as DPoS (Delegated Proof of Stake). Those run about a hundred high powered servers, 20 that act as regular super nodes + 1 out of the other hundred chosen randomly. Each one is voted in by people who have a stake (other coin holders). It's decentralized by the stake holders, but the delegates are intentionally limited to 21, or 53, or some other odd number.

I can't give you more info as that's my understanding of it at the moment. Someone else needs to chime in, or a search should turn up something.
sr. member
Activity: 781
Merit: 276
I'm hodling another altcoin that uses zerocoin and masternodes. Might be easier to implement than zkSnarks. I recognize one or two names here who also have that altcoin, but that's off-topic here. Smiley

If it is a potential enhancement for GUN, it is fair game to discuss here.  zkSnarks are one option that we are considering and have done some very recent research on.  However, at this point, we have not thought too much about the implementation.  But the premise is interesting and there may be others who have better knowledge of it or have other similar options for us to think about.
legendary
Activity: 3416
Merit: 1912
The Concierge of Crypto
I'm hodling another altcoin that uses zerocoin and masternodes. Might be easier to implement than zkSnarks. I recognize one or two names here who also have that altcoin, but that's off-topic here. Smiley
sr. member
Activity: 781
Merit: 276
I was curious how the coin was allotted to the market at that time and its price had been on the floor for quite a long time


I have read this several times, and I'm not sure exactly what you're asking.

??


We get a lot of "drive-bys" with newbies looking to pad their post numbers.  If you check them out, you will see they post about a dozen times in a matter of minutes on a dozen threads.  In some cases, it has nothing to do with the thread they post in.  Even if you responded, chances are they will never see it and never come back.
sr. member
Activity: 539
Merit: 255
I was curious how the coin was allotted to the market at that time and its price had been on the floor for quite a long time


I have read this several times, and I'm not sure exactly what you're asking.

??
member
Activity: 101
Merit: 10
I was curious how the coin was allotted to the market at that time and its price had been on the floor for quite a long time
Pages:
Jump to: