Topic: ⚒ Syscoin -Blockchain Scalability, Trustless Interoperability for ERC20 projects - page 127. (Read 501963 times)

Latest syscoin is segwit capable if miners include witness blocks it will work. Thx ill check out csv.. ill make sure its enabled in next release.

what does 'Segwit signalling support' mean? I get following lines when I ask Syscoin Core for getblockchaininfo:
"segwit": {
      "status": "started",
      "bit": 1,
      "startTime": 1479168000,
      "timeout": 1510704000
    }
startTime and timeout are just the same as bitcoin. Does that mean syscoin will activate segwit at the exact same time as Bitcoin? Or is it an independent adoption process like Litecoin?
(I also noticed, at least under BIP 9, CSV is not activated yet and there are only 2-3 months left until the timeout because the setting is the same as bitcoin, which seems too short.)

Putin's hack 

Thanks danosphere, sebastien1234 and bontol72 for your replies  

I'll ask in Slack for any further advice before attempting to upgrade from sysversion "2.10"

Hi there, the domain has not expired, today was the renewal date and the site is fine from North America, however there seems to be a DNS issue from other parts of the world, we assume it will only take some time to repropagate the DNS but we are looking into the nature of the issue to ensure this does not happen again.

Oh they paid those coins to the btc utxo at a snapshot time. How does that help anyone holding syscoins at that time?

Hey whats up with your website (http://syscoin.org/), seems as if it has expired?  Was this planned, or just an oversight (understandable).  Not great PR during this crucial time.

No, it's a real coin .. you can acquire by proving your btc balance .. when snap shot coming just link your btc balance at chat bot in wallet and yu will receive bytes and blackbytes .. after you can sold out them for btc.

So...when's the next big update/ release/ development/ announcement coming ?
We really need something to get the price to the next level and have it stay there.
This spiking and then dropping back down again is getting pretty frustrating imo...

Oh cool.. so you mean through an asset?

im sorryfor that 

if syscoin team need funds for development watched to byteballs..its a free token..please go read announcement if you want do free benefice.

https://bitcointalk.org/index.php?topic=1608859.0;topicseen

good luck

You not only should do as @sebastien1234 suggested but you should also upgrade to the latest core- https://github.com/syscoin/syscoin2/releases/tag/2.1.2. Click the zip link if you're on windows, DMG link if you're on Mac.

Looks like you're running some older version of SYS, current core version is 0.13.2 and if you run "getinfo" from console you should see Syscoin version 2.1.2. If you join us in slack we can provide more direct assistance  

Please join us in slack for troubleshooting.

join.syscoin.org

You still need to delete all your old data before upgrading. Of course backup your wallet.dat first then delete all the old files under roaming/appdata/Syscoin and try again. Please join us in slack for troubleshooting.

join.syscoin.org

need help wallet stops sync at block 29999, already tried a lot of stuff and still the same cant bypass block 29999

the latest version 2.1.2: https://github.com/syscoin/syscoin2/releases/tag/2.1.2

presumably if your wallet has synchronized to the right height (currently 82178) then by definition you're on the right chain. I ask because the Syscoin version I'm running is
 v0.13.00.0-dc8186d (64-bit)..... and I'm easily confused. Do I need to upgrade?

We are not on 2.0 chain anymore so 2.0 transactions are invalid you need to clear your db when upgrading to 2.1.

2.0
https://chainz.cryptoid.info/sys20/address.dws?1KhTcoZYNXbuUWcYm5sXhet15CG8JW8pU1.htm

2.1.1
https://chainz.cryptoid.info/sys/address.dws?1KhTcoZYNXbuUWcYm5sXhet15CG8JW8pU1.htm

Hello.
We experience the following issues after updating of SYS node to 2.1.2 version:
1. Issues with answer to getinfo request: "errors": "Warning: unknown new rules activated (versionbit 28)"
2. Mismatch of transactions in the node and in our database (some of transactions have disappeared from node). Let's take a look at this address for example:
"address": "SfzTeeLh6to6zpQ1JWrcFZ2ZiyVZ6BFZiC",
"v2address": "1KhTcoZYNXbuUWcYm5sXhet15CG8JW8pU1",

According to our database the following transactions were successfully processed by a node:

24.99980000000000 7760adf39a21e8d7d042c2b28ff6b37c10470823eb0485f7f8dd31d19257a403
49.99980000000000 55d9e925e5bc433710a0c9b212966ee9cb4021235de2c561a11e312ae9fc015f
19.99980000000000 09519675a3d131b37e6e4010e39a97f86389278ad4987c3c5c51cd19fe139a8d
29.99980000000000 cc67ea69306b4ba8539d1bc1698275f52e03e072c22e7f4c8130b321b6e27486
133.5272000000000 647863d09179faaa64ae17655eb6d636bf6e108d7d84f1f562e2b972555626f3
181.4923000000000 f8c10696b683f218ad8c16c21c1d6cab6bfef241ebd89b904a67f06379ebad87
299.9998000000000 8349d0e7a6e2e1add2a667e7bd6b39fbc55a1e41e2715c729b435b219961f32f
99.99979999999999 60112f5b1bdbce2e4c371b673b5cd8fcd9a49e356bc2e9d1d766a6dc3eef60bd
64.06980000000000 5f7315d65ee128f3ec4b3fa7fbf2126790ebf0ff55bc942468c5bd145c636acc
33.73980000000000 8ba067f9f06dffe4eaed4ca078eb1f3b2cd39d0e42e8fbbe035992bbd89a5e3b
400.5998000000000 627a2ac1fecbcbe3a884211ac76780642f8264c15f3033111b97e9fe5c109802
499.9998000000000 a7fcabcfc6a735a60765dfbaef0f6264c0ba4974b1198e297e3f20b425f79d85
399.9998000000000 cd795c6815c8660201fe86d7126f90b4852eefb1b0e12c69ce632696cf9ac943
421.6358000000000 fb1bac9d69ef66ea88dd6916a3fbd9f8bc5e53212d3d60abc55fe994c4b09ef3
436.3880000000000 bffe7f0c8619490a0bbd2caed691c4065bf2c6128a43d7e71eee29079d4501a3
436.3880000000000 8607c645b44f4f42e9cf333dce3b5e9344e1233744603f7f5f0c5e170390ada5

While node and block explorer has only one transaction:
436.3880000000000 8607c645b44f4f42e9cf333dce3b5e9344e1233744603f7f5f0c5e170390ada5

Is that a fork or what is going on?