[ANN] Signatum - New Algorithm - Fair Launch - No Premine

[easyrimka]

whats happened with cryptopia ?? how are we supposed to withdraw if there was no annoucement 

[1714683483]

1714683483

[1714683483]

1714683483

[1714683483]

1714683483

[1714683483]

1714683483

[xtraelv]

Delist Notice: Signatum
As the vast majority of Signatum customers will be aware, there have been recent issues with this coin, which has led to us putting it in the delisting queue. Signatum is currently scheduled to be delisted on 20 Oct 2017. Read on for the reasons why this has been deemed our best course of action at this time.

The combination of us having 18,000 addresses and users mining directly to our addresses caused there to be over a million small inputs. This caused the wallet to irreparably break while syncing. We attempted to resolve this many times, using different distros and hardware configurations, however this did not work. If we synced the blockchain first, then imported the keys, it would start importing 5-10 keys / second, however this rate drops to about 1 key every 3-4 seconds after ~15k. After a week of importing keys on several instances the wallets corrupted and crashed every time. We also tried importing the keys first then syncing the blockchain, in this case it synced back to around 19th August and then also crashed and corrupted.

We have determined this to be likely due to the leveldb library used within the coin which is extremely out of date. It is the same library used in many other coins, however most use a much more up to date version.
This is why the Signatum wallet had been in maintenance for around the last month, while we have been constantly attempting to work with it. During this time, we had a Signatum team member visit our office in person and found no issues with our implementation of Signatum, and observe the sync issues. We have also been in constant communication with a Signatum team member informing of what was happening throughout and were told by him that he was informing the rest of their team.

To finally resolve this, we have managed to set up 8 separate wallets and imported 1/8 of the overall keys into each of these. We then had to move transactions around to consolidate the tiny inputs. This is a terribly painful process and not scalable.

FYI we are currently having to move coins from the 8 wallets to 1 consolidated wallet to process withdrawals. Once this process is complete, we will then scan the 8 wallets for any missing deposits, so anyone that has made deposits while it has been in maintenance will have to wait until this before their deposits show up so they can withdraw again.(edited)
The reason we are now closing the markets is that the Signatum community and now the core Signatum team have blamed us for this issue and are threatening us with litigation, when the issue is purely with the Signatum wallet and out of date codebase. The dev does not seem able or willing to fix the issues with their code. We have put in a very significant amount of time trying to get this up and running so our users can use their coins. However, it is not our responsibility to work with the Signatum codebase (or any other coin) to fix their problems any further, we've already gone well beyond what we should be doing to resolve this.

Some users have been comparing us to other exchanges and asking why they don't have a similar problem. We have a significantly higher number of transactions than the other exchanges that currently list this coin. They will run into similar issues when they reach a more significant level of transactions. The problem with Signatum codebase is provable and replicable. They need to fix this or this will happen again wherever Signatum ends up.

Signatum now appears to also be threatening Cryptopia with legal action (via twitter) and accusing Cryptopia of not knowing how to use wallets. We run and maintain literally many hundreds of wallets. Signatum built just 1 wallet by copying very old code from elsewhere and don't seem able or willing to update it to something that actually works at scale. Draw your own conclusions, and if you back Signatum after all this good luck to you.

Published by: Hex @ 9/19/2017 2:49:29 AM

https://www.cryptopia.co.nz/News

Regardless of where the fault lies, a major exchange has now put this out there about SIGT. The SIGT team is going to have to fix the problems described should they exist, or make some other changes if they don't. Whatever is done needs to be sold to people as a faster & more efficient SIGT. They have to do something and make it very public they did something in order to rebuild confidence and move beyond this.

Is this true that signatum is not scalable? That they are using an out if date codebase? This makes me nervous for the long term if this is true

The project is open source and you can check the source code online. https://github.com/signatumd/source. Appears that Sigt is using leveldb for backend database, specifically version 1.17, released in May 2014. As of now the newest version is 1.20. Per Cryptopia guys said this db was outdated, true. They say it's been outdated for 6 years, false. Was this causing the Cryptopia wallet problem, uncertain but yes according to their response. Will this outdated db cause any other problems, uncertain. Are there any other coins using the same db with the same version and have no issues so far, don't know but worth looking around(maybe I will later). Should the devs update this db, should.

That is as far as I know. Would really like to hear more from the devs and sigt community. Should you sell or hold is up to you.

Where does it say 6 years in his statement ? I only see where he says it is extremely outdated.

[oisilener1982]

B6wREFoeS9hAFvFTrPvdddkhvhDxBAz1v8   17 876 000 SIGT

Someone is holding 17.8 Million SIGT.

[WarrenP]

whats happened with cryptopia ?? how are we supposed to withdraw if there was no annoucement 

Here is a link to cryptopia official news on Sigt.
https://www.cryptopia.co.nz/News

[WarrenP]

B6wREFoeS9hAFvFTrPvdddkhvhDxBAz1v8   17 876 000 SIGT

Someone is holding 17.8 Million SIGT.

Hopefully it is a Cryptopia wallet that they are using to consolidate the wallets and transactions as per the news:
https://www.cryptopia.co.nz/News

[coreshift]

Delist Notice: Signatum
As the vast majority of Signatum customers will be aware, there have been recent issues with this coin, which has led to us putting it in the delisting queue. Signatum is currently scheduled to be delisted on 20 Oct 2017. Read on for the reasons why this has been deemed our best course of action at this time.

The combination of us having 18,000 addresses and users mining directly to our addresses caused there to be over a million small inputs. This caused the wallet to irreparably break while syncing. We attempted to resolve this many times, using different distros and hardware configurations, however this did not work. If we synced the blockchain first, then imported the keys, it would start importing 5-10 keys / second, however this rate drops to about 1 key every 3-4 seconds after ~15k. After a week of importing keys on several instances the wallets corrupted and crashed every time. We also tried importing the keys first then syncing the blockchain, in this case it synced back to around 19th August and then also crashed and corrupted.

We have determined this to be likely due to the leveldb library used within the coin which is extremely out of date. It is the same library used in many other coins, however most use a much more up to date version.
This is why the Signatum wallet had been in maintenance for around the last month, while we have been constantly attempting to work with it. During this time, we had a Signatum team member visit our office in person and found no issues with our implementation of Signatum, and observe the sync issues. We have also been in constant communication with a Signatum team member informing of what was happening throughout and were told by him that he was informing the rest of their team.

To finally resolve this, we have managed to set up 8 separate wallets and imported 1/8 of the overall keys into each of these. We then had to move transactions around to consolidate the tiny inputs. This is a terribly painful process and not scalable.

FYI we are currently having to move coins from the 8 wallets to 1 consolidated wallet to process withdrawals. Once this process is complete, we will then scan the 8 wallets for any missing deposits, so anyone that has made deposits while it has been in maintenance will have to wait until this before their deposits show up so they can withdraw again.(edited)
The reason we are now closing the markets is that the Signatum community and now the core Signatum team have blamed us for this issue and are threatening us with litigation, when the issue is purely with the Signatum wallet and out of date codebase. The dev does not seem able or willing to fix the issues with their code. We have put in a very significant amount of time trying to get this up and running so our users can use their coins. However, it is not our responsibility to work with the Signatum codebase (or any other coin) to fix their problems any further, we've already gone well beyond what we should be doing to resolve this.

Some users have been comparing us to other exchanges and asking why they don't have a similar problem. We have a significantly higher number of transactions than the other exchanges that currently list this coin. They will run into similar issues when they reach a more significant level of transactions. The problem with Signatum codebase is provable and replicable. They need to fix this or this will happen again wherever Signatum ends up.

Signatum now appears to also be threatening Cryptopia with legal action (via twitter) and accusing Cryptopia of not knowing how to use wallets. We run and maintain literally many hundreds of wallets. Signatum built just 1 wallet by copying very old code from elsewhere and don't seem able or willing to update it to something that actually works at scale. Draw your own conclusions, and if you back Signatum after all this good luck to you.

Published by: Hex @ 9/19/2017 2:49:29 AM

https://www.cryptopia.co.nz/News

Regardless of where the fault lies, a major exchange has now put this out there about SIGT. The SIGT team is going to have to fix the problems described should they exist, or make some other changes if they don't. Whatever is done needs to be sold to people as a faster & more efficient SIGT. They have to do something and make it very public they did something in order to rebuild confidence and move beyond this.

Is this true that signatum is not scalable? That they are using an out if date codebase? This makes me nervous for the long term if this is true

The project is open source and you can check the source code online. https://github.com/signatumd/source. Appears that Sigt is using leveldb for backend database, specifically version 1.17, released in May 2014. As of now the newest version is 1.20. Per Cryptopia guys said this db was outdated, true. They say it's been outdated for 6 years, false. Was this causing the Cryptopia wallet problem, uncertain but yes according to their response. Will this outdated db cause any other problems, uncertain. Are there any other coins using the same db with the same version and have no issues so far, don't know but worth looking around(maybe I will later). Should the devs update this db, should.

That is as far as I know. Would really like to hear more from the devs and sigt community. Should you sell or hold is up to you.

Where does it say 6 years in his statement ? I only see where he says it is extremely outdated.

Hi,

The SIGT wallet is now available for withdrawals. Any pending deposits will be processed as soon as we can, you will need to withdraw these again ASAP once they are processed. The markets will remain closed and SIGT is still going to be delisted.

SIGT is based on a 6 year old code base and does not cope with the volume of transactions and addresses generated by it's community. It doesn't have an active developer and a resolution to this problem is unlikely.

Please check our News page for a more in depth statement: https://www.cryptopia.co.nz/News

We apologize for the delay in getting SIGT back up however we were dealing with issues out of our control. Good luck with your future trades!

Please be patient while we finish working on the wallet and try not to log anymore tickets, we love talking with you guys but it does make it more difficult to get your issues resolved when we are flooded with tickets ;-)

Thanks,
Jerry
Cryptopia Support

Jerry was referring to the code base. Not specifically the DB version.

[cryptobaht]

B6wREFoeS9hAFvFTrPvdddkhvhDxBAz1v8   17 876 000 SIGT

Someone is holding 17.8 Million SIGT.

Hopefully it is a Cryptopia wallet that they are using to consolidate the wallets and transactions as per the news:
https://www.cryptopia.co.nz/News

Or maybe it's Doc lol

[z0rn]

Delist Notice: Signatum
As the vast majority of Signatum customers will be aware, there have been recent issues with this coin, which has led to us putting it in the delisting queue. Signatum is currently scheduled to be delisted on 20 Oct 2017. Read on for the reasons why this has been deemed our best course of action at this time.

The combination of us having 18,000 addresses and users mining directly to our addresses caused there to be over a million small inputs. This caused the wallet to irreparably break while syncing. We attempted to resolve this many times, using different distros and hardware configurations, however this did not work. If we synced the blockchain first, then imported the keys, it would start importing 5-10 keys / second, however this rate drops to about 1 key every 3-4 seconds after ~15k. After a week of importing keys on several instances the wallets corrupted and crashed every time. We also tried importing the keys first then syncing the blockchain, in this case it synced back to around 19th August and then also crashed and corrupted.

We have determined this to be likely due to the leveldb library used within the coin which is extremely out of date. It is the same library used in many other coins, however most use a much more up to date version.
This is why the Signatum wallet had been in maintenance for around the last month, while we have been constantly attempting to work with it. During this time, we had a Signatum team member visit our office in person and found no issues with our implementation of Signatum, and observe the sync issues. We have also been in constant communication with a Signatum team member informing of what was happening throughout and were told by him that he was informing the rest of their team.

To finally resolve this, we have managed to set up 8 separate wallets and imported 1/8 of the overall keys into each of these. We then had to move transactions around to consolidate the tiny inputs. This is a terribly painful process and not scalable.

FYI we are currently having to move coins from the 8 wallets to 1 consolidated wallet to process withdrawals. Once this process is complete, we will then scan the 8 wallets for any missing deposits, so anyone that has made deposits while it has been in maintenance will have to wait until this before their deposits show up so they can withdraw again.(edited)
The reason we are now closing the markets is that the Signatum community and now the core Signatum team have blamed us for this issue and are threatening us with litigation, when the issue is purely with the Signatum wallet and out of date codebase. The dev does not seem able or willing to fix the issues with their code. We have put in a very significant amount of time trying to get this up and running so our users can use their coins. However, it is not our responsibility to work with the Signatum codebase (or any other coin) to fix their problems any further, we've already gone well beyond what we should be doing to resolve this.

Some users have been comparing us to other exchanges and asking why they don't have a similar problem. We have a significantly higher number of transactions than the other exchanges that currently list this coin. They will run into similar issues when they reach a more significant level of transactions. The problem with Signatum codebase is provable and replicable. They need to fix this or this will happen again wherever Signatum ends up.

Signatum now appears to also be threatening Cryptopia with legal action (via twitter) and accusing Cryptopia of not knowing how to use wallets. We run and maintain literally many hundreds of wallets. Signatum built just 1 wallet by copying very old code from elsewhere and don't seem able or willing to update it to something that actually works at scale. Draw your own conclusions, and if you back Signatum after all this good luck to you.

Published by: Hex @ 9/19/2017 2:49:29 AM

https://www.cryptopia.co.nz/News

Regardless of where the fault lies, a major exchange has now put this out there about SIGT. The SIGT team is going to have to fix the problems described should they exist, or make some other changes if they don't. Whatever is done needs to be sold to people as a faster & more efficient SIGT. They have to do something and make it very public they did something in order to rebuild confidence and move beyond this.

Is this true that signatum is not scalable? That they are using an out if date codebase? This makes me nervous for the long term if this is true

The project is open source and you can check the source code online. https://github.com/signatumd/source. Appears that Sigt is using leveldb for backend database, specifically version 1.17, released in May 2014. As of now the newest version is 1.20. Per Cryptopia guys said this db was outdated, true. They say it's been outdated for 6 years, false. Was this causing the Cryptopia wallet problem, uncertain but yes according to their response. Will this outdated db cause any other problems, uncertain. Are there any other coins using the same db with the same version and have no issues so far, don't know but worth looking around(maybe I will later). Should the devs update this db, should.

That is as far as I know. Would really like to hear more from the devs and sigt community. Should you sell or hold is up to you.

For me leveldb looks like Version 1.2 but this is from 2011-05-16 as mentioned here: https://github.com/signatumd/source/blob/master/src/leveldb/NEWS . This is pretty near to 6 years. But it also says "Fixes for larger databases (tested up to one billion 100-byte entries,
i.e., ~100GB)" . I will investigate further.

[mystere_miner]

For me leveldb looks like Version 1.2 but this is from 2011-05-16 as mentioned here: https://github.com/signatumd/source/blob/master/src/leveldb/NEWS . This is pretty near to 6 years. But it also says "Fixes for larger databases (tested up to one billion 100-byte entries,
i.e., ~100GB)" . I will investigate further.

It is confusing, and I can see how some people might have looked at the code and thought it was 6 years old.

The actual version number in db.h is 1.17, as well as the version  number in the makefile.

[coreshift]

What's interesting to me is the SIGT network (and block explorer) was working just fine while Cryptopia was consolidating all those wallets & addresses. Why didn't the network get overloaded then? That would likely be the highest workload it ever experienced, right?

[AlexNT01]

It is already Final.

SIGT is to be Delisted @ Cryptopia especially with the DEVS threatening cryptopia

Did I miss some important messages? What have devs threatened cryptopia?

Anyway, cryptopia is now able to withdraw, since they can sync with wallet now, then I really don't get it why signatum has to be delisted?

DEVS of SIGT said they will SUE cryptopia

yea they should sue cryptopia, why not? Hell why not sue spoons cause they made you fat too? The devs of SIGT can never be wrong after all right? It's always someone else's fault. sue earth or the clouds for it raining today, sue the government for using it's weather control device too! If something goes wrong with SIGT it can't EVER be apparent incompetence of SIGT devs. Nope it's GD  Santa's fault for not bringing the right color of army men when that one SIGT dev was 7 years old! (you know who you are) THEY WANTED THE DARK GREEN ONES!  I mean EVERYONE KNOWS THE TAN COLORED army men ARE THE FUCKING EVIL ONES AFTER ALL!  

[AlexNT01]

What's interesting to me is the SIGT network (and block explorer) was working just fine while Cryptopia was consolidating all those wallets & addresses. Why didn't the network get overloaded then? That would likely be the highest workload it ever experienced, right?

Cause apparently SIGT is too revolutionary based on version 0.9 BTC code that of course cryptopia is singling SIGT out! It's like Warren Buffet said TRAINS ARE THE FUTURE OF TECHNOLOGY!

[coreshift]

What's interesting to me is the SIGT network (and block explorer) was working just fine while Cryptopia was consolidating all those wallets & addresses. Why didn't the network get overloaded then? That would likely be the highest workload it ever experienced, right?

Cause apparently SIGT is too revolutionary based on version 0.9 BTC code that of course cryptopia is singling SIGT out! It's like Warren Buffet said TRAINS ARE THE FUTURE OF TECHNOLOGY!

So, you have no idea why Cryptopia consolidating didn't cause the SIGT network to overload. Got it.

[dodopool]

Please do STOP talking about leveldb if you don't know what it is. Cryptopia had to blame something and found this...
it is a very simple KV store that can and will hold a lot more rows that cryptopia can dream to have. (even the older versions)
Stop pasting readme files which are not updated (if you are a developer of any kind you should be familiar with documentation not being updated)

here is signatum leveldb version 1.17 https://github.com/signatumd/source/blob/master/src/leveldb/include/leveldb/db.h#L16

here is dash version 1.18
https://github.com/dashpay/dash/blob/master/src/leveldb/include/leveldb/db.h#L16

here is ethereum.... wait for it... version 1.2
https://github.com/ethereum/leveldb/blob/windows/include/leveldb/db.h#L15

[AlexNT01]

What's interesting to me is the SIGT network (and block explorer) was working just fine while Cryptopia was consolidating all those wallets & addresses. Why didn't the network get overloaded then? That would likely be the highest workload it ever experienced, right?

Cause apparently SIGT is too revolutionary based on version 0.9 BTC code that of course cryptopia is singling SIGT out! It's like Warren Buffet said TRAINS ARE THE FUTURE OF TECHNOLOGY!

So, you have no idea why Cryptopia consolidating didn't cause the SIGT network to overload. Got it.

it's cause cryptopia is targeting SIGT, I mean this coin is so cool and fad and hip and jiggy and stupid and punk and phat and yuge and rad and awesome and dope and yo and farout and suchwow and ripped!

[thin]

So, you have no idea why Cryptopia consolidating didn't cause the SIGT network to overload. Got it.

But now network is really unstable.  What is the reason?

[coreshift]

So, you have no idea why Cryptopia consolidating didn't cause the SIGT network to overload. Got it.

But now network is really unstable.  What is the reason?

It's not people mass withdrawing from Cryptopia (since they can't withdraw) and it's not a massive increase in trading or mining. Other than that, I don't know.

[oisilener1982]

My Poor 7.9 SIGT was just added to Yobit from Cryptopia

It arrived like 4 or 5 hours after it was confirmed @ Cryptopia but at least I can see it now @ Yobit

[xtraelv]

Which is the real Signatum ? Aren't these supposed to be sequential ?

[AlexNT01]

I saw a picture that would seem to show at least 4 if not more then 4 different chains going on... GD Cryptopia! how dare you break this coin with your "normal usage" this coin wasn't designed on fiver for such use!
GREAT!
$5 shot to hell!