Hi, I would like to ask a question: Have you guys checked whether Spectre is affected by the recent Bitcoin vulnerabilities? (CVE-2018-17144) Would be cool to have a statement on this.
The above vulnerability (CVE-2018-17144) was as a result of changes introduced in Bitcoin Core 0.14 and as Spectrecoin is built around a previous version on Bitcoin Core this does not apply to our code base. |
|
|
|
|
Hi everyone. I will try to keep this thread updated a bit more. We will update the ANN and the info shortly...
|
|
|
|
A new thread and coin appeared: https://bitcointalk.org/index.php?topic=5054438.0They call themselves Spectre Security Coin, SPECTRE for short and their Twitter name is 'SpectreCoin' and they want to use the ticker 'XSPC'. They are simply trying to impersonate an established project, Spectrecoin ( https://spectreproject.io). Spectrecoin has been using SPECTRE for short since 2016 and are using the ticker 'XSPEC'. It is clear that when they want to use the ticker ' XSPC' and the same name as the real Spectrecoin / SPECTRE to sell masternodes it must be considered a possible scam. Why would a serious project use near identical identifiers as a long established project? To cause confusion in order to sell their masternodes. Compare and make up your own mind: The REAL established project:Name: Spectrecoin (short SPECTRE) Ticker: XSPEC Purpose: Serious privacy coin with long term active development GitHub: https://github.com/spectrecoin/spectreThe impersonating project:Name: SpectreSecurityCoin (short SPECTRE), Twitter name: SpectreCoin (only difference a capital C) Ticker: XSPC Purpose: selling masternodes GitHub: 404 error IMO https://bitcointalk.org/index.php?topic=5054438.0 - SpectreSecurityCoin is a scam attempt and a clear rip-off of name and ticker to cause confusion. |
|
|
|
|
So calling your Twitter 'SpectreCoin' with a capital C when we are 'Spectrecoin' and short your Discord to SPECTRE when we have used SPECTRE since 2016 and use a ticker 'XSPC' when we use 'XSPEC' is a pure coincidence, yes?
My only question is why you chose name, ticker and abbreviation that is virtually the same as ours? You didn't answer that. You just said that we don't have a monopoly.
So, why choose a name that you know will cause confusion?
Until then this is obviously a SCAM!!!
|
|
|
|
Please click on any link in the above ann msg. It will take you to our website so you can learn more about our group and project. Thanks!  What can you learn about this team? What do you think?  Who are these people? Where are the contacts? Thank you for asking. Hop in on our Discord Channel https://discord.gg/YaWbSv to know more about us! We are actively answering all your questions there. Why do they not address these questions: Why choose that name on Twitter when there is an established project already? Why choose a ticker that is almost the same? This is a deliberate attempt to confuse people and steal their money |
|
|
|
This one has a really nice use case. Security is very important.
It's simply a rip-off - wake up and see the scam!!! They are using our name and a similar ticker to confuse people. |
|
|
|
This is a sick joke!!!! Total SCAM!!!!
WE ARE SPECTRE!!! https://spectreproject.io/We are SPECTRE and Spectrecoin. We have been Spectre / Spectrecoin since 2016 and we are a serious project and not some masternode scam trying to rip off our name. Your Twitter even says 'SpectreCoin' and you use the ticker 'XSPC' when we use the ticker ' XSPEC' - this is not due to useless and lazy research but clearly a rip-off.  IF YOU ARE IN ANY WAY SERIOUS YOU RE-NAME AND RE LAUNCH. You will not get on exchanges we are with that name and ticker.
|
|
|
|
|
It's a ridiculous idea to punish masternode operators if their VPS has a crash and then force operators to buy more coins to start again
|
|
|
|
so I did the math.... and according to this calculatorin 2 days when block reward hits 5 coins per block (25 times what it is currently... ie .2 coins/block) at current difficulty, 1000 staked coins generates (.3688*25) or just over 9 coins a day. hmmm, I'd venture to say the folks who held spreadcoins in local wallet at snapshot rather than Cryptopia must be getting a warm fuzzy right about now.... https://www.heliumchain.info/#/pos/1000and I guess that the rest of us with coins in Cryptopia feel left behind by the team and feel that the team could have handled this better and not just put the blame on Cryptopia. So, some (a minority it seems) with a warm fuzzy feeling and the majority feel cheated. Not good I believe for the future. The team should have had all this dealt with before launching. It's too easy to just point the finger at Cryptopia. How can the helium devs make cryptopia exchange admins do anything, all they can do is ask, and nag, and I assume they're doing both everyday. On another issues, is staking returns competitive with running masternode? I was thinking of a more professional approach than asking and nagging, where the devs talk to Cryptopia prior to launch and negotiate an agreement and maybe wait to release the wallets until Crytopia is ready to open the Helium market and deposits / withdrawals. Nagging sounds like a bunch of toddlers.... |
|
|
|
so I did the math.... and according to this calculatorin 2 days when block reward hits 5 coins per block (25 times what it is currently... ie .2 coins/block) at current difficulty, 1000 staked coins generates (.3688*25) or just over 9 coins a day. hmmm, I'd venture to say the folks who held spreadcoins in local wallet at snapshot rather than Cryptopia must be getting a warm fuzzy right about now.... https://www.heliumchain.info/#/pos/1000and I guess that the rest of us with coins in Cryptopia feel left behind by the team and feel that the team could have handled this better and not just put the blame on Cryptopia. So, some (a minority it seems) with a warm fuzzy feeling and the majority feel cheated. Not good I believe for the future. The team should have had all this dealt with before launching. It's too easy to just point the finger at Cryptopia. |
|
|
|
|
I can confirm this, I'm the project manager for coin and YoBit has zero communication and do not update in time and we have had that problem many times in the past so we just advice people to stay away from YoBit for our coin.
Good work by the way with Syscoin...
|
|
|
|
We all waited patiently for close to a year (well maybe not that patiently, but whatever...) for this launch...
Now let's not all get our panties in a twirl over a few more days wait for the Cryptopia market to open.
days^^ its more like weeks  ITS cryptopia. the problem is the guys what have the coins in wallet have already set up the masternodes and we lose money..  Well, you are not loosing money but rather not earning it  but I feel ya. I don't have coins locked, because I wasn't participating in snapshot, but I would also like to start masternode before the rewards will increase. what is the difference between not earning and losing money  ? if i can generate coins but not doing it i lose money or not  ? ~6 days until the normal rewards kick in. so cryptopia have 5 more days. there is a little bit hope but not much. What I don't get though, is that the team can't provide a one line update. Confirm that it's Cryptopia that's holding back and not some other problem. I know everyone is busy but it only takes 5 min for a quick update and the latest response they had from Cryptopia. I'm the project manager for a coin listed on Cryptopia and when I contact them about wallet issues etc. they normally get back to me in a day or so with a response. |
|
|
|
for what cryptopia needs so long? if they dont open helium soon there is no longer a fair start. im sure the normal rewards starts before this shit exchange do anything...
I think the dev team could provide an update with some info about why it is taking so long when the chain is running for a while now. They must have been in communication with Cryptopia and there must be a reason why it's taking so long. |
|
|
|
While our progress with the Business Platform is moving forward in the background, we expect to finish and start testing it by the end of september. Until then, we have some exciting new developments to share with you. After roughtly talks with our community, we decided to change the specification of the network. We think this is an important update for our future plans and also for the long run benefits.
Starting from block 300,000 Seesaw algorithm will be removed, coin emission rate will be decreased, masternode collateral will be increased and block rewards will be adjusted to: 70% for MNs and 30% for stakers.
New specifications:
from block 300,000 to block 386,400 – 9 synx per block (2 months) → MN Collateral: 5,000
from block 386,400 to block 472,800 – 8 synx per block (2 months) → MN Collateral: 10,000
from block 472,800 to block 559,200 – 7 synx per block (2 months) → MN Collateral: 15,000
from block 559,200 to block 645,600 – 6 synx per block (2 months) → MN Collateral: 20,000
from block 645,600 to block 732,000 – 5 synx per block (2 months) → MN Collateral: 25,000
!!! Once you start your Masternode with the ‘Current Required Collateral’ (5.000 SYNX), your Masternode STAYS RUNNING when collateral increases. If you stop your Masternode and want to start a new one in the future, you will need to have the Required Collateral.
Besides this important update, Luka is working on wallet improvements and minor bugs fixes.
What’s coming next ?
1. A brand new explorer which is expected to be available before the end of September
2. Business Platform release which is expected for the month of October
3. A wallet redesign for a better user experience before the end of the year
Just to clarify please, so if my MN is running past block 386,400 (10,000 collateral point) and then my VPS crashes and I have to re-start my MN, I need to increase the collateral? |
|
|
|
|
Is there any more information as to when Cryptopia will open for Helium so we can start running some MNs?
|
|
|
|
|
Hi, good luck with the project. So, you dev, Moonshot, is he now working for both Phore and Helium?
|
|
|
|
|
Whats the reward for a single MN for 24 hrs on average, in AXE?
|
|
|
|
...
if you would read the minimum documentation that is present you would find same ipv6 support as in Dash/etc. maybe you need to prepare better before setting up a masternode? we are trying to protect the community from spammers and etc, these parties are very active recently Now that you know I'm not a scammer, this is what I get when I try to start the MN: Alias: MN01
Failed to start masternode.
Error: Invalid IP address This is the IP address, same as set in the axe.conf on the VPS: [2a03:b0c0:1:d0:fb89::1]:9937 So, from that I am assuming that there is no IPv6 support, thats why I was asking... There is no IPv6 support for Axe. This is intentionally done to prevent multiple MN's running on same VPS Thats all I wanted to know, thank you, is there a ROI calculator somewhere? |
|
|
|
...
if you would read the minimum documentation that is present you would find same ipv6 support as in Dash/etc. maybe you need to prepare better before setting up a masternode? we are trying to protect the community from spammers and etc, these parties are very active recently [/quote] Now that you know I'm not a scammer, this is what I get when I try to start the MN: Alias: MN01
Failed to start masternode.
Error: Invalid IP address This is the IP address, same as set in the axe.conf on the VPS: [2a03:b0c0:1:d0:fb89::1]:9937 So, from that I am assuming that there is no IPv6 support, thats why I was asking... |
|
|
|
|
Show Posts
