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

We would love to help, however, there's really nothing we can do about Yobit not responding to your request. I can tell you however that May 1st, 2016 at 10AM PST, we forked Syscoin and had advised all exchanges including yobit of it several days prior to and gave them the go-ahead for the launch. The only way to reach them was via a support ticket or twitter; I personally attempted several times to get in touch with them to no avail. Finally June 12th, 2016, they advised us that their wallet had been updated to the new chain.

What does this mean? We really are not sure what YoBit will do, they allowed trading/deposits/withdrawals on an old chain for a month and a half, anything that happened on the old chain after the Syscoin 2.0 launch is not valid on the new chain. They did not reach out to us and did not seem concerned about the situation in their response.

I wish you the best and hope Yobit will honor your trades and give you the coin owed to you as this is completely their mistake.

Hi

Can someone help me resolve an issue with transaction on Yobit Exchange?

I made a withdrawal of some SYS from my wallet on Yobit to my wallet on Bittrex exchange.

2016.05.12 21:18:51    SYS    17147.57641459    0    In process

As you can see I made it more then a month ago, but it still does not complete.
I can say more, this order does not have an ID. So i think it didn't even get to the network.

I created many tickets, waited for a month. After a month support closed all my tickets and said that if the issue is still not resolved, than create new ticket.
I created a new ticket 2 weeks ago. But there is still no answer from support and the issue is not resolved.

Any help?

Why such a dodgy background in that update? Anything to do with lisk?

edit:
Now I know I think

EXPANDED MARKETPLACE OFFERINGS
Revisit research done prior to the 2.0 launch on ETH and other decentralized DApp platforms. Based on the updated findings explore porting the Syscoin offerings to new platforms in a way that would allow all existing Syscoin products to be reused, providing instant value. Explore use of sidechains.

http://syscoin.org/roadmap/

Development Update #3 – June 12, 2016  - Tweeted!

https://twitter.com/jeveuxdire/status/742711268834988032

Thanks for the update! I am holding it since day 1

I have decided to invest in and support Syscoin 

July is going to be a VERY interesting month in the crypto world...

thats because BTC is up... sooo much

Development Update #3 – June 12, 2016

We’ve made a lot of progress on development over the last week and we’ve updated the roadmap to try and get everything in place in time for certain Microsoft events with as little change to existing release target as possible.
 
As mentioned last week resources in terms of developers are scarce and we don’t want to spend a lot of SYS dev funds at these prices to on board something equivalent to full time help. We are talking with a few developers we’ll try to leverage as supplemental support but in planning we’re still operating as if its just the two internal devs we have at present. These same resources are needed to setup the company entity which we need in order to proceed expanding our relationship with Microsoft. We had some tough decisions to make because the Microsoft conference is coming very soon, and Syscoin 2.1 is also very close to being ready for release with several new features.
 
To best utilize resources we’ve decided to scope back the Blockmarket release for June to a pretty simple “lite” version that simply shows balance, and allows users to send and receive in the same simple login/setup/deployment framework that the full Blockmarket will use. We’re doing this just to satisfy the Microsoft requirements in time for the conference. The plan was a full Blockmarket beta for June. Because a beta won’t work for our Microsoft endeavors we’ve scaled back to a lite, non-beta release for June with the full release still planned for late July as previously planned. With the additional resources gained from scoping back the June release of Blockmarket we’ll increase the testing effort behind Syscoin 2.1, and be able to get the company setup. We still plan on releasing Blockmarket lite to the public sometime before the end of June. This plan gives us the best shot of being part of the MSFT conference, the requirements of which we just learned about last week.
 
Assuming all testing goes smoothly on Syscoin 2.1 we’ll be releasing that June 26th, 2016. Syscoin 2.1 will be a mandatory update and we’ll coordinate with exchanges and miners around its release. By holding off on the full Blockmarket release until after Syscoin 2.1 we’re also maximizing efficiencies as it relates to Blockmarket dev- because the new Syscoin release introduces many new commands and modifies some existing commands if we release Blockmarket ahead of 2.1 we’d incur work just weeks later on the back end of the 2.1 release to deal with these changes. The full Blockmarket release is targeted for July 24th, 2016 and will include some of the features introduced in 2.1. We’re not sure if there will be a beta of the full Blockmarket at the moment- we’ll reasses our resources in July to make that decision.
 
These hard target dates allow us to better coordinate our PR efforts. In conjunction with our PR partners we’re already working on marketing around 2.1 and the full Blockmarket release- we’ll be running our own efforts in parallel with those of our PR partners to ensure the best results; Blockmarket being the larger of the two releases/efforts. All of these updates have already been applied to our roadmap.

http://syscoin.org/dev-update-3/

I know Dans working on this but im pretty sure you can derive keys through deterministic wallets using a passphrase or brainkey. The accounts in the wallet should be locked to these brainkeys. It should be similar to how counterparty web wallet works. You wouldn't want to have your private keys stored on anywhere but your computer.

I'm wondering if this is related in some way to the problems with SYS & p2pool?

Just guessing of course......

Still the same 6 transactions at 6.78kB sat in the memory pool. Clearly this is not a network propagation issue,  as these are not my transactions. It seems like miners are not picking up the transactions. I'll keep an eye out on when zpool solves a block (not very often) to see if that pool picks them up.
As I typed this, I saw a transaction come in and get included in the next block. Same 6 txs at 6.78kB just sat there.

EDIT: Or maybe there is some kind of network propagation issue, since no node appears to have rebroadcast my flushed transaction.

Will the private keys be stored on a hosted web wallet or on the client side?

For now yes... in Blockmarket V2 you will be able to  login to a web interface that is hooked up to the blockchain and get your private keys through a hosted web wallet (stored keys in javascript so your safe).. this way people don't have to have nodes running and can buy and sell things on the global marketplace (meant for small retailers). Larger wholesalers or merchants will probably want their own blockmarket with custom branding or perhaps a ecommerce store with a Syscoin plugin talking to the blockchain with a payment gateway to Syscoin.

With Sys 2.1 I've added pruning so new nodes syncing will only ever have to download the data of services which are not expired (1 year default time for expiry). You can extend expiration by updating the services to keep the from expiring and being pruned on the network.

Jag

Is the market integrated in SYS wallet?

Is it necessary to download the whole SYS blockchain to buy/sell on SYS market?

Explorer shows correct balance on all 3 addresses, which are conversion address balances.

Explorer shows a balance for your address? Try sending to yourself?

I tried sending 4 times. 2 on linux build from source, 2 from latest windows binary. Each time the transactions where broadcast, but don't know if they will be rejected as double spends from the first one. Currently no nodes have rebroadcast my transaction that I have now backed out from the wallet.
My debug window still shows the same 6 at 6.78 kB transactions in the memory pool.
Did see a very large free transaction (kB size wise) go through yesterday.

Never had this issue.. interesting.. is it reproducible everytime?

The old nodes aren't issue cause they are on different chain.