As has been repeated several times- beta SYS are just SYS for testing. They cannot be sent to mainnet, they cannot be sold. Buy some SYS in the market or mine some with the MAINNET wallet (on op and website) then you can transfer and exchange/sell much as you want. Beta SYS are just like testnet Bitcoin. They have no value. |
|
|
|
Hey new to sys community.
where is this movement coming from?
price predictions?
Syscoin has been underpriced for ages. We're a legit coin with features and functionality no other coin offers. That said our market cap has been <1mil$ basically for forever. If you look at coinmarketcap there are lots of straight up clone coins with ZERO innovation that have market caps >Syscoin. My guess is that people get a clue as to the scale and possibilities the Syscoin 2.0 platform offers that our market cap will grow to reflect that. Not gonna shoot for this price or that price, just saying our marketcap even at 1mil is very undervalued imho. |
|
|
|
Syscoin.org is down. What happened?
It's working here. Seems okay... This is what I'm seeing:  [/quote] Apologies, I renewed the domain and then our registrar botched something. Will be back in 48hrs or less so they say! The blockchain syncing is taking ages, is there a bootstrap file?
There isn't yet, but I can get one together for ya. I'm prett tied up with sys2 rested work today, could I get u the bootstrap Tomm? |
|
|
|
Just like I said a week ago... anyone cares to move a few coins to Poloniex ? The volume is too small..
I do all my trading on polo to try and get more volume over there. BTC38 has a surprising amount of volume! It's a good thing! |
|
|
|
Coin Supply During PoW Phase: 64,800,000
PoW appears to last for 180days then we go into a series of PoS tiers. Exactly. Pos specifications will be decided in next weeks, as far as I understood. hopefully dev keeps PoS coins low, 64mil is plenty in PoW given its duration. Rest should just be inflation to keep things moving. |
|
|
|
Coin Supply During PoW Phase: 64,800,000
PoW appears to last for 180days then we go into a series of PoS tiers. |
|
|
|
User information is secured using encryption with SHA512. We do not store funds on the same server as the site database so in the event that the site is compromised, neither funds or user information will be useful or available to attackers.
Buyers and Sellers communicate through the website. Email notifications will be sent when gigs are purchased.
Buyers are protected from fraudulent service providers through escrow, the number of days specified for delivery would be stated and locked in once the order has been made. In the event that there is a dispute, the order can either be cancelled by the seller or the dispute is raised and we will look at the dialogue ourselves to resolve the matter.
This is the information I was looking for, thank you. Essentially you've created a token to go alongside your/BitHire's centralized web implementation of a service marketplace which happens to depend on the HIRE token. I was trying to understand how the services BitHire offers relates to the functionality of the coin/the blockchain and your reply helps me to better understand (per my understanding- they aren't related outside the fact $HIRE is used to facilitate payment). Can you elaborate on the "bitcoin integration" you mentioned? How does that work with $HIRE? is it just an exchange based on current HIRE/BTC rates or something more? Thanks, wish you and other freelancers on the the BitHire platform the best of luck. Extra exposure never hurt a freelancer afaik  |
|
|
|
Clearly you've misunderstood the whole idea behind this project. The coin has nothing to do with "tech" innovation. They have never claimed to be that. They are simply using existing tech to transfer value and promote user content on the platform.
They might have plans to add coins development down the line but this was never intended or mentioned and is not to be expected of them. Perhaps a coin like factom or ETH is what you are looking for. I welcome any coin development and think it would bring even more value to users but it's a little harsh to criticise their project in a somewhat condescending manner.
People are investing time (freelancers, listing gigs) and $$ (investors, ppl trying to use the coin to buy gigs) in this thing, I don't think its harsh at all to ask the developer of the project technical questions. Even if there is no innovation here (which is what you're saying) they still should have answers to these questions- how will they provide any type of support if things start to go wrong? They're using existing tech, ok- what coin was this forked from? Or what assimilation of coins was it birthed from? |
|
|
|
As I am holder of SYS1, can you enumerate the final method of conversion to SYS2?
Happily! We aimed to make the process as simple as possible, simply export your SYS1 private key, import it into the SYS2 wallet one released, and you'll get the appropriate coins based on your SYS1 balance. If you coins are on exchange, this will happen automatically. There is no expiration date on converting your coins. Let me know if you have any other questions |
|
|
|
Yeah right not touching this price manipulated coin right now lmao. Nice trex pump and all, for those that will win...yet anyone buying now will lose and baghold. If this coin is real it is/can be promising though...but with that manipulation it REALLY turns ppl off knowing that isn't real btc pushing it up. Nobody knows about this coin and it flies just like that??  this. Edit: - poor website - ANN has no technical info - whitepaper is simply a marketing roadmap, NOT a whitepaper. - oversupplied ICO - code had SIX commits. Total. Trivial changes. - pumped out of the gate Why don't you post some real technical info? Why should freelancers even waste time w Bithire? Why no just list their services on CoinToPay, accept any crypto they want, and avoid Bithire bag holding entirely?? A whitepaper is not limited to only delivery of technical concepts. Its clear, you seem to be more technically inclined which is fair but again, building a service product doesn't require a full technical overview. When the project started, we wanted to solve some problems we identified with current services for freelancing and we observed a niche that could be filled with our service. Clearly, our website is different to CoinToPay and we've chosen to go about the route of settling directly in Crypto and not in fiat. I'm not going to go into depth why that has its benefits, we've all heard that before. Other services like fiverr have integrated crypto payments and also settle in fiat. Infact, they raised $60M in series D funding just do integrate this. Many websites, reddit, zapchain changetip etc. have mechanisms for allowing micro-transactions and micro-tipping. And HIRE is in line with that idea. It also served as an opportunity for us to kick-start this project. Whilst you could argue that users can perhaps get the same from other websites, I would argue that dealing with fiat is something we have chosen to sidestep and thus position ourselves as crypto-only. Furthermore, there is absolutely no reason why having more options to sell their services on other platforms is a problem at all. Especially given that the incumbent competition all settle in fiat and have some what of a oligarchy going on. As for bag holding Bit hire, we are committed to giving holders the opportunity get real services on a platform where for once, they can do something with the coin instead of as you say bag holding. Again, it is another option and we are not a fault for giving people that option. We have been running social media (see our twitter, facebook) for several months now, and I know plenty of community members here will back us up in saying that there is genuine interest in the project. I don't know and therefore can't comment on what happens with the coin out the gate, but what we're focusing on doing is continually to update the site and build something that people truly would like to use. If you have further questions, I will do my best to answer them. Thanks for the reply and i certianly am not questioning your commitment to the project (with a pump like that out of the gate why wouldn't you be comitted) but unfortunately your reply is a lot of words without the technical content I'm looking for / which is included in the OP or first few replies of most altcoin ANNs. Can you please provide technical information about the coin itself and its underlying technology? - 1. What makes this better than any other clone coin? The code in github doesn't show many changes from the standard clone coin that will be dumped in a month.
- 2. How are you storing data on chain? Are you even storing data on chain?
- 3. How are you protecting again bloat?
- 4. How are you securing buyer information?
- 5. Is buyer information stored on chain?
- 6. How do buyers and service providers communicate- is this in wallet or pushed to some third party service like email?
- 7. I see images on listings, are these stored on chain?
- 8. How does the "bitcoin integration" work?
- 9. How do you support buyers from fraudulent service providers? What happens if I pay for a gig but it is never completed, is there some refund or escrow mechanism to secure (what is essentially trustless) service provider/consumer interaction?
All of the above questions are things I would expect answered in a meaningful whitepaper, especially one that's about a crypto marketplace for freelancers. Some of these are very serious issues when it comes to a marketplace and marketplace security, speaking from experience here. Your whitepaper doesn't touch on any of these, not even on a surface level, and that's ok- if you can answer the above questions. I'm looking for real tech innovation to invest in, can you tell me how $HIRE accomplished that in a meaningful way? Please include specifics, and don't talk to the marketing plans, social media, the freelance community, how you'll make this coin valuable for everyone long term, your commitment, etc. While that's all good and well that isn't what I'm inquiring about. As the developer and distributor of a coin, answering these questions in a succinct and technical manner should be pretty basic. I've numbered them to make it a lil easy to tie you answers with the related questions- Thanks! |
|
|
|
Will return to 500 sat  Not very likely... What's the reasoning behind your negative opinion here? 500 sats is a market cap of ~$830K which doesn't seem very high to me, especially considering the valuations of other projects that are at a much earlier stage. You can disregard that. Should have said "Very likely." Should not try to do more than 4 things at the same time while posting...  And with the decreased coin count in SYS2 and some enumeration of how many SYS1 are converted to SYS2 maybe we can get a realistic picture of the SYS economy rather than it being "~400mil coins mined thus far... give or take 50-100million SYS lost by the escrow provider.". You can see on the block explorer/richlist that many of the largest wallets haven't been accessed in over a year, we suspect they never will be accessed due to the failures of our original escrow provider (this is speculation atm, based on presale buyers who reached out to us complaining they were locked and/or never got their private keys from the escrow provider). --- Been a while since I swung through here but seb/key/sidhujag been keeping ppl updated. Things are looking very positive for SYS, our last team mtg which took place on Monday involved identifying a number of milestones related to getting current services / exchanges / pools ready for the cutover in addition to reaching out to new services and exchanges that we'd like to announce as SYS2.0 moves to mainnet. As Keyare mentioned things are on track for a final public beta within the next two weeks. Given this we do expect to have Syscoin 2.0 on mainnet sometime in March so long as nothing major (in terms of bugs) is discovered. While the public tries to break the final beta we'll be reaching out to merchants and service providers so there is some initial population of the marketplace, and its not barren on launch  Even though a lot of people think about a marketplace as a place for purely goods the SYS offer design supports services as well! If you or your friends have services you'd like to offer in exchange for BTC/SYS/USD/etc those services can be offered, advertised, resold (if enabled!) and procured all using the SYS marketplace. Additionally the SYS marketplace gives you escrow options and secure communication using SYS keys (no need for 3rd party encryption, just as secure as PGP without needed to use PGP). These features- aliases, escrow, price pegging, reselling and encrypted messaging are all things we wanted to have in the initial delivery a year ago but simply didn't have the bandwidth, time, or expertise (at the time). Its been a year now- working on SYS for free and holding our coins as we've worked towards a more complete realization of our original vision. Now that time is nearly at hand. With so many feature and capabilities I definitely am on the lookout for the public testing revealing issues we may not have caught internally. But, I am very confident any issues found will be minor because in the process of the upgrading the core from 0.8 -> 0.11.2 we actually wrapped many of the service features that SYS adds in unit tests, increasing my confidence in the features and their stability immeasurably and dramatically reducing our regression testing cycles (if you're in software dev, you know!). Things are lining up and we're plannin on turning on the long-sleeping marketing machine gradually as we ease into this weekend, building momentum from there. This weekend we also plan on releasing additional information about some of the features we've alluded to but not fully disclosed (yet). If you are a freelancer looking to offer your services, or a merchant looking to leverage/gain additional exposure and sales via the SYS decentralized marketplace, please reach out to us- we want to help you get setup and answer any questions you may have!And of course of you have questions please ask here, on our reddit, our slack or twitter  |
|
|
|
|
My masternodes are all running smoothly and paying out as expected, nice work dev. Looking forward to future plans.
|
|
|
|
Yeah right not touching this price manipulated coin right now lmao. Nice trex pump and all, for those that will win...yet anyone buying now will lose and baghold. If this coin is real it is/can be promising though...but with that manipulation it REALLY turns ppl off knowing that isn't real btc pushing it up. Nobody knows about this coin and it flies just like that?? this. Edit: - poor website - ANN has no technical info - whitepaper is simply a marketing roadmap, NOT a whitepaper. - oversupplied ICO - code had SIX commits. Total. Trivial changes. - pumped out of the gate Why don't you post some real technical info? Why should freelancers even waste time w Bithire? Why no just list their services on CoinToPay, accept any crypto they want, and avoid Bithire bag holding entirely?? |
|
|
|
When i type 'masternode winners' I'm seeing "Unknown" for the last 9 or so blocks. Is this what other people on the network are seeing or is something wrong with my wallet/controller wallet. I'm running several masternodes so if something is incorrect, I'd like to know! Thanks! |
|
|
|
Try the darknet-qt in src/qt.
Add the nodes from op. My win wallet didn't need the addnodes, the linux one didn't connect without.
Thank trying to do this but need to build from source to get that darknet-qt to show up in src/qt... tried building from source and got this error/output stream: Making all in src
make[1]: Entering directory `/root/Darknet/src'
make[2]: Entering directory `/root/Darknet/src'
CXX libbitcoinconsensus_la-allocators.lo
CXX primitives/libbitcoinconsensus_la-transaction.lo
CXX crypto/libbitcoinconsensus_la-hmac_sha512.lo
CXX crypto/libbitcoinconsensus_la-sha1.lo
CXX crypto/libbitcoinconsensus_la-sha256.lo
CXX crypto/libbitcoinconsensus_la-sha512.lo
CXX crypto/libbitcoinconsensus_la-ripemd160.lo
CXX libbitcoinconsensus_la-eccryptoverify.lo
CXX libbitcoinconsensus_la-ecwrapper.lo
CXX libbitcoinconsensus_la-hash.lo
CXX libbitcoinconsensus_la-pubkey.lo
CXX script/libbitcoinconsensus_la-script.lo
CXX script/libbitcoinconsensus_la-interpreter.lo
CXX script/libbitcoinconsensus_la-bitcoinconsensus.lo
CXX libbitcoinconsensus_la-uint256.lo
CXX libbitcoinconsensus_la-utilstrencodings.lo
CXXLD libbitcoinconsensus.la
CXX darknetd-darknetd.o
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[2]: *** [darknetd-darknetd.o] Error 4
make[2]: Leaving directory `/root/Darknet/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/Darknet/src'
make: *** [all-recursive] Error 1
Any ideas?  How much RAM do you have available? I usually see "g++: internal compiler error: Killed (program cc1plus)" compiling on Raspberry Pi with too many cores and I run out of RAM. I think it might be this, let me try upping the ram and giving it another go |
|
|
|
Try the darknet-qt in src/qt.
Add the nodes from op. My win wallet didn't need the addnodes, the linux one didn't connect without.
Thank trying to do this but need to build from source to get that darknet-qt to show up in src/qt... tried building from source and got this error/output stream: Making all in src
make[1]: Entering directory `/root/Darknet/src'
make[2]: Entering directory `/root/Darknet/src'
CXX libbitcoinconsensus_la-allocators.lo
CXX primitives/libbitcoinconsensus_la-transaction.lo
CXX crypto/libbitcoinconsensus_la-hmac_sha512.lo
CXX crypto/libbitcoinconsensus_la-sha1.lo
CXX crypto/libbitcoinconsensus_la-sha256.lo
CXX crypto/libbitcoinconsensus_la-sha512.lo
CXX crypto/libbitcoinconsensus_la-ripemd160.lo
CXX libbitcoinconsensus_la-eccryptoverify.lo
CXX libbitcoinconsensus_la-ecwrapper.lo
CXX libbitcoinconsensus_la-hash.lo
CXX libbitcoinconsensus_la-pubkey.lo
CXX script/libbitcoinconsensus_la-script.lo
CXX script/libbitcoinconsensus_la-interpreter.lo
CXX script/libbitcoinconsensus_la-bitcoinconsensus.lo
CXX libbitcoinconsensus_la-uint256.lo
CXX libbitcoinconsensus_la-utilstrencodings.lo
CXXLD libbitcoinconsensus.la
CXX darknetd-darknetd.o
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[2]: *** [darknetd-darknetd.o] Error 4
make[2]: Leaving directory `/root/Darknet/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/Darknet/src'
make: *** [all-recursive] Error 1
Any ideas? |
|
|
|
|
I'm trying to spin up a darknet wallet on an ubuntu box, I pulled down the latest DNET linux wallet, installed the dependencies and from what i can tell I'm supposed to run ./darknet-cli. When i ran it the first time it complained about no .conf, so I put that in place and now it just spits out "error: couldn't connect to server" when i run ./darknet-cli start. Any suggestions? Works fine on OSX and Windows...
|
|
|
|
Awesome thanks very much! |
|
|
|
Any good tutorials on how to setup a DNET masternode? Seems like a bunch of incomplete ones from other coins, would love to help out but not super familiar with masternode setup TIA |
|
|
|
Thanks guys Today I'm very busy. I need to finish up the final round of applications for funding in a startup corporation I'm involved with. Once I get past this I'll try to do some more work with Swing. Again, thank you all for your support. Welcome back bro! |
|
|
|
|
Show Posts
