Mark I sent you a PM.
Many thanks for the message  |
|
|
|
Ok so everyone needs to keep calm and carry on. What's an ETA for CPU Argon2d? Not the 3-6 months as stated earlier?
As stated earlier, just sounds like you guys need a lead project manager to report to and adjust target date times as needed if issues occur.
You have lots of developers but no single entity to pull all end points to a final target date and communication is a key factor.
You all have always delivered, but you need someone to pull the developers together and if shit falls thru, as the coding world always does, that person needs to be the community informant as well since there has been communications break downs.
I work in logistics/transportation for 16 years. It's all about communication and managing several components from supply chain to customer end delivery. It's a clusterfuck and the worst industry ever as far as stress and failure. If I can manage a shit storm on a day to day basis, you guys can certainly find someone to help manage your objectives better.
P.S. As an example you'd be surprised how complicated it is just to get something as simple as milk on your store shelf.
Also I think most users might be confused by the initial time frame given. Not knowing there was background communication going on and things were being adjusted in order to lessen a huge delay.
We are always open for more active community members that can bring in experience.  |
|
|
|
Ico is over ?
tell me ico price ?
Countdown has been down to 0 for some time now. Final result $ 0.25 per DSLK. |
|
|
|
No i could care less about this project. Failed ico. Would like my bitcoins back if there will be any extended delay on release. Are my funds not in escrow as promised? Or did i misread the escrowed ico thing?
Too bad you feel that way. I've send you a pm, let's continue there. so much for "transparency" does this "team" even know what that word means? nope their do busy trying to mop up truthers as seen here... smooth... I am taking my time to speak to every single one of you in person so that i can accommodate better to private situations while keeping the public slate as clean as possible. i know that if a person is calm and at ease he would post less clutter, this is not about keeping things in the dark but about lending out support and taking things up personally. |
|
|
|
No i could care less about this project. Failed ico. Would like my bitcoins back if there will be any extended delay on release. Are my funds not in escrow as promised? Or did i misread the escrowed ico thing?
Too bad you feel that way. I've send you a pm, let's continue there. |
|
|
|
almost every ico have delay's... it's "normal".
but yeah, no communication is a problem... they should at least explain what happened.
but chill guys, wait a little before you start crying and asking for your money back... it's a big launch and a small team, one day isnt big deal.
Sorry about the lack of communication. Please wait for an official announcement but yes, there has been issues and a release delay. I am (or was if I don't get kick off) on the dev team and agree that we should have communicated our issues earlier. Days ago, I suggested that we let the community know about our issues and potential release delay but was overruled and/or ignored. This is no way to conduct business and gain trust.  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Orestes please tell me again there is no issues with the team.. i honestly thought higher of you. And you will even higher after this weekend. I know why you are upset though. It is because you want this project to succeed, like we all do. It is because of this that you dared to invest, just like us. It is not the increased risk of loss that grieves you, it is the possible loss of the project. But that is a fallacy! The team is very much joined together and we will continue as usual. Now the production process that Silk Network has used because if its small size clearly is outdated and needs to be transformed. Much in the style MCDev pointed out. What has happened to use multiple times is that we had a public failure, much like this. But because community membery really do believe in this project, instead of forsaking it, they join in and help where they can. It's how I joined, and some others. Where it breaks, it grows stronger. The project needs more capable men(preferably rich in experience), we always do, but we will pull through regardless. It just might take a bit longer... brick by brick. |
|
|
|
Argon2d has no fast-verify code and it will take between 3-6 months to get it implemented as we need to write it from scratch.
Here is where he didnt say 2-3 months, said 3-6 months.. In either case where a project was supposed to be released a month after the ico, one might think that this issue of writing this from scratch, and the non-existance of fast-verify would have been known long before we opened our wallets up. This project promised transparency, accountibility, a sense of community, and a team of dedicated developers to release a asset backed security by todays date. ANY question relating to the interests of the ico holders should be answered in a timely fashion, especially in times of failure, or witholding key information that would negatively affect the securities you sell at the weaver. You cannot have one foot into corporate and one foot out into crypto.. either both feet in or stay decentralized kids so accountibility is important here.. if it wasn't me and many others would not have invested into athe silk network ltd. Public offering via the weaver. As funds were held in escrow until release (as i read) this should not be an issue in refunding investments. I couod see a week or two or a month even, but well into next year with no certain date, with a team falling apart, and an unknown name or title for the project, in the midst of a corporate dissolution and new incorporation... is completely and absolutely unacceptable. You guys stepped up to the big boys plate, so please act like adults and the crypto geniuses you claim to be, both in coding and business. Would be appreciated. Good luck on the home stretch and take these words into serious consideration. Dontigua we were having an ICO on the development of a crypto token based system that behaves like: 1 a currency, 2 an asset. Yet they remain crypto-tokens. The team is not falling apart, we are only dealing with blowback due to a sudden delay in release. Please refrain from being the cause of a problem that doesnt really exist. |
|
|
|
In an earlier but recent post (1688) I stated “I don't think there are too many people who realize the amount of time and effort it takes to get a project like this running. So far they have done a lot better then I thought they would.”
Reading the posts when it became evident that the release wasn’t happening on 11/5 as originally planned, it really makes that statement resonate. It is almost as if any new altcoin project needs to qualify “investors” based not only on their altcoin investing experience, but their project management in the software industry or experience as a developer.
I am not saying anyone who is complaining or asking for refunds of the BTC submitted for the ICO doesn’t have investing experience, you very well could have that experience. With that experience, however should come caution, a lot of questions, and above all assumption of all risk for any ICO. I have a great deal invested in this project in terms of the legacy Silkcoin I had in Poloniex and the amount of Silk I bought on Bittrex as my confidence level grew from in all honesty 25%-30% to the 95% where it is now. And that 5% gap is where the qualification of knowledge of the software development process comes into play. And that 5% gap is not whether I think this project will succeed, it’s the impact on the project not reaching its 6 month potential value due what appears to be the lack of knowledge of the software development process.
The only fault I can push to the project is the fact that they do not have their management plan fully implemented. The developers, lead developers included should not be required or expected to be communicating in the forum or chats regarding schedules or where the development process is. That is the job of the project manager or scrum master. The developers have much more important things to do with their time.
In any large development project, the project plan (based on complexity of the project) has at minimum three (3) stages where a replan is evaluated based on the status of the project. That replan would have triggered an announcement of a delay.
This project is not a simple wallet with the specific features they announced. Its two wallets, Weaver (which basically looks like an exchange to me), an entire network backbone, and I lost count of the additional pieces. The wallets and Weaver basically had to follow the waterfall methodology for the initial releases because each could not be developed and released using the Agile methodology. The problems with waterfall is that you are almost certain to miss even the least aggressive schedules because waterfall is prone to a bug, bugs, or issue occurring at the final stage or even final testing cycles. That is why Agile is now the industries answer to that problem. Release incremental small, releases that show immediate value to the users.
Read that last line again… RELEASE INCREMENTAL, SMALL RELEASES THAT SHOW IMMEDIATE VALUE TO THE USERS. This projects success relies on user acceptance, not the will or ROI of the investors. Investing in this or any project (even other than crypto) is pointless unless there is a user base, otherwise, where does the value come from? Hype? That is not what this project offered. It offered a strong user base which required the rebranding to ensure that user base.
The dev team appears to be at near the completion of the third waterfall project; Dark wallet (Silk and Weaver already released and functional). I think going forward they will be using a more Agile approach and we will see regular releases that meet scheduled release dates.
I don’t think anyone has stated there would be a 2 to 3 month delay in Dark. If I missed that, it’s due to being very tired right now. I just canceled 5 BTC in Silk buy orders so I have that extra to buy Dark when it opens for trading.
For those who are saying they want their BTC back, I am sure that you will be able to sell off your Dark to those of us who know the value of the project and will be waiting to buy them from you. It’s up to you if and when you sell them and at what price, however if you were in the ICO for short term gains, you may not get a 100% return of your investment, long term, you like the rest of us in it for long term gains will see a nice ROI.
Sorry for rambling on… I got pissed seeing some of the negative posts after the announcement of the delay and realizing the fact that the 150 or so BTC collected (BTC and Silk) for the ICO amounts to what, under 20 BTC when split between the 8 members of the team. And what, accusations that the team is ripping investors off, for what 14 to 15K, and ruining their reputations. These guys have been around for quite a while and I think their reps are worth more than that to them.
Thank you MCDev for that post. It shows great insight and experience to the developmental process. Overal your message surely should be taken to heart by the community. |
|
|
|
Just relax and have some faith in the dev team, they will get this worked out.
The team is made of code warriors. What this means is they will try to battle out problems before letting the problem get to them. It narrows down vision in the believe that the battle will be won. We're all in agreement that communication should be guided better, but those that take up the fight, they rather fight then talk about it... I guess they lost this fight, but I've seen the process they go through and am convinced that the battle will be won. |
|
|
|
I understand the codebase for Darksilk will be released on the 5th of november. Is there any more known about the rebranding and the release on Bittrex?
DSLK will be released on the 5th, Bittrex will follow soon after launch. After they've done their due diligence. We are patiently awaiting the rebrand, what we do know is that it embodies a new direction for the project as a whole without interfering current developments/technologies. |
|
|
|
everywhere and everybody talking about darksilk, anybody here who can tells us about the future of SILK, At present neither price increase nor volume of SILK
SLK and DSLK are chains that will both be heavily utilised by the Silk Network platform. The OP is full of information regarding this, please start there... also people like to chase moving trains instead of daring to invest in a ticket... |
|
|
|
Now that i know these addresses are not "dead" also realized that: - the wallet has multiple addresses and they are all mine
- If I add them all they will give me the total on the wallet
- I can create as many as I want in the receiving menu clicking the new button
- If the balance is 0 there will be an error in the explorer for that address
- If you send some coins to it, it will show up OK
Thanks Orestes you're the man Only if it has never had a transaction before. Confirmation creates the address on the chain i think, old 0-addresses can exist. |
|
|
|
Thanks but as I said I know the coins are there so I'm not worried
Just wanna clear few things up about how this wallet works
And I do have the privkey for the initial addresses of the wallet
but those addys don't exist anymore but they show in Receiving
Error! : Search found no results for: Sh7LdoD2m1vzVhVn18pUjcn.....
send 1 SLK to it, maybe that helps |
|
|
|
Use coin control to see which inputs have a value.
Export the private key of those addresses (dumpprivkey).
In coin control menu I have 456 entries 450 with the same address used when I split the coins 6 others that I never new they existed, not labeled and all with some amounts in them Selecting them all will give me the Available amount displayed on the wallet The total amount is bigger with the amount staking right now, I guess it's another address somewhere for that So again which one is the right one? and If i export all with values then I have to recover(just in case of trouble) each of them, one by one, and then add the values? You could also send all coins to a new wallet and back up that privkey. Is there any reason to hold a specific address? Or send the 6 blocks to the 450 address. Anyways for every address there is a privkey. So if you want to split your coins over multiple addresses then you would need to store multiple privkey's. |
|
|
|
Yes I deleted the older version I had on my computer thinking I could fix it by downloading a brand new one from the Silknetwork.org this morning and there is problems with it that the devs need to fix as this will definately cause loss of confidence in the project for people that are not tech savy. We just want to be able to download and have an automated idiot proof (fool proof) wallet that will work and if this is not achievable I believe the project is doomed to tell you the truth.
addnode=159.203.111.196 addnode=45.32.7.212 addnode=84.195.38.128 addnode=195.200.244.73 addnode=47.208.182.225 addnode=163.172.42.67 addnode=209.122.15.66 try these from the peerslist |
|
|
|
I have another question. This question is about the new coin Silk. I downloaded the win64 wallet and I have no active connections. I have let it run for 2 days, nothing, not 1 connection and I am not sure what is wrong. Every other time I have downloaded a wallet they usually get an active connection and start downloading the chain within minutes??? is Silk still in working progress? does Silk only exist in the Weaver at this current time? confused a little, some clarity would be much appreciated.
You might need to add Silk.conf to your Silk folder as well if you want to add nodes, getpeerinfo gives [
{
"id": 1,
"addr": "159.203.111.196:16662",
"addrlocal": "82.73.172.120:59751",
"services": "0000000000000001",
"lastsend": 1477775769,
"lastrecv": 1477775768,
"bytessent": 217497,
"bytesrecv": 191055,
"conntime": 1477746955,
"pingtime": 0.192541,
"version": 60800,
"subver": "Silk Core:1.0.0",
"inbound": false,
"startingheight": 57539,
"banscore": 0,
"synced_headers": 57975,
"synced_blocks": 57975,
"inflight": [
],
"whitelisted": false
},
{
"id": 3,
"addr": "45.32.7.212:16662",
"addrlocal": "82.73.172.120:59758",
"services": "0000000000000001",
"lastsend": 1477775780,
"lastrecv": 1477775780,
"bytessent": 70253,
"bytesrecv": 89426,
"conntime": 1477746968,
"pingtime": 0.139018,
"version": 60800,
"subver": "Silk Core:1.0.1",
"inbound": false,
"startingheight": 57539,
"banscore": 0,
"synced_headers": 57975,
"synced_blocks": 57975,
"inflight": [
],
"whitelisted": false
},
{
"id": 4,
"addr": "84.195.38.128:16662",
"addrlocal": "82.73.172.120:59761",
"services": "0000000000000001",
"lastsend": 1477775793,
"lastrecv": 1477775793,
"bytessent": 91859,
"bytesrecv": 97156,
"conntime": 1477746979,
"pingtime": 0.061508,
"version": 60800,
"subver": "Silk Core:1.0.0",
"inbound": false,
"startingheight": 57539,
"banscore": 0,
"synced_headers": 57975,
"synced_blocks": 57975,
"inflight": [
],
"whitelisted": false
},
{
"id": 5,
"addr": "195.200.244.73:16662",
"addrlocal": "82.73.172.120:59766",
"services": "0000000000000001",
"lastsend": 1477775812,
"lastrecv": 1477775812,
"bytessent": 84392,
"bytesrecv": 92515,
"conntime": 1477746996,
"pingtime": 0.09001199999999999,
"version": 60800,
"subver": "Silk Core:1.0.1",
"inbound": false,
"startingheight": 57539,
"banscore": 0,
"synced_headers": 57975,
"synced_blocks": 57975,
"inflight": [
],
"whitelisted": false
},
{
"id": 6,
"addr": "47.208.182.225:16662",
"addrlocal": "82.73.172.120:59767",
"services": "0000000000000001",
"lastsend": 1477775809,
"lastrecv": 1477775809,
"bytessent": 80325,
"bytesrecv": 88940,
"conntime": 1477746997,
"pingtime": 0.246048,
"version": 60800,
"subver": "Silk Core:1.0.1.1",
"inbound": false,
"startingheight": 57539,
"banscore": 0,
"synced_headers": 57975,
"synced_blocks": 57975,
"inflight": [
],
"whitelisted": false
},
{
"id": 7,
"addr": "163.172.42.67:16662",
"addrlocal": "82.73.172.120:59793",
"services": "0000000000000001",
"lastsend": 1477775783,
"lastrecv": 1477775783,
"bytessent": 81323,
"bytesrecv": 98301,
"conntime": 1477747091,
"pingtime": 0.204542,
"version": 60800,
"subver": "Silk Core:1.0.0",
"inbound": false,
"startingheight": 57540,
"banscore": 0,
"synced_headers": 57975,
"synced_blocks": 57975,
"inflight": [
],
"whitelisted": false
},
{
"id": 8,
"addr": "[2601:100:8000:5c20:3543:4804:d0e7:34a4]:16662",
"addrlocal": "[2001:0:9d38:6ab8:1475:33eb:adb6:5387]:59823",
"services": "0000000000000001",
"lastsend": 1477775791,
"lastrecv": 1477775791,
"bytessent": 62962,
"bytesrecv": 78171,
"conntime": 1477747220,
"pingtime": 0.196042,
"version": 60800,
"subver": "Silk Core:1.0.0",
"inbound": false,
"startingheight": 57542,
"banscore": 0,
"synced_headers": 57975,
"synced_blocks": 57975,
"inflight": [
],
"whitelisted": false
},
{
"id": 10,
"addr": "[2001:0:9d38:90d7:38ac:10a4:adb6:5387]:54450",
"addrlocal": "[2001:0:9d38:6ab8:1475:33eb:adb6:5387]:16662",
"services": "0000000000000001",
"lastsend": 1477775754,
"lastrecv": 1477775754,
"bytessent": 79458,
"bytesrecv": 72204,
"conntime": 1477754385,
"pingtime": 0.006001,
"version": 60800,
"subver": "Silk Core:1.0.0",
"inbound": true,
"startingheight": 57642,
"banscore": 0,
"synced_headers": 57971,
"synced_blocks": -1,
"inflight": [
],
"whitelisted": false
},
{
"id": 11,
"addr": "209.122.15.66:16662",
"addrlocal": "82.73.172.120:60467",
"services": "0000000000000001",
"lastsend": 1477775751,
"lastrecv": 1477775751,
"bytessent": 56939,
"bytesrecv": 77549,
"conntime": 1477754499,
"pingtime": 0.693123,
"version": 60800,
"subver": "Silk Core:1.0.1",
"inbound": false,
"startingheight": 57645,
"banscore": 0,
"synced_headers": 57975,
"synced_blocks": 57975,
"inflight": [
],
"whitelisted": false
},
{
"id": 12,
"addr": "[2001:0:5ef5:79fb:2cfa:c5:9d5b:ac29]:53441",
"addrlocal": "[2001:0:9d38:6ab8:1475:33eb:adb6:5387]:16662",
"services": "0000000000000001",
"lastsend": 1477775758,
"lastrecv": 1477775758,
"bytessent": 62027,
"bytesrecv": 73722,
"conntime": 1477754508,
"pingtime": 0.237045,
"version": 60800,
"subver": "Silk Core:1.0.1.1",
"inbound": true,
"startingheight": 57645,
"banscore": 0,
"synced_headers": 57975,
"synced_blocks": -1,
"inflight": [
],
"whitelisted": false
},
{
"id": 16,
"addr": "[2001:0:9d38:90d7:20f6:e2b:a12c:dbeb]:49299",
"addrlocal": "[2001:0:9d38:6ab8:1475:33eb:adb6:5387]:16662",
"services": "0000000000000001",
"lastsend": 1477775775,
"lastrecv": 1477775775,
"bytessent": 60997,
"bytesrecv": 50355,
"conntime": 1477766770,
"pingtime": 0.107512,
"version": 60800,
"subver": "Silk Core:1.0.0",
"inbound": true,
"startingheight": 57826,
"banscore": 0,
"synced_headers": 57975,
"synced_blocks": -1,
"inflight": [
],
"whitelisted": false
},
{
"id": 24,
"addr": "[2001:0:9d38:6ab8:188b:19ca:bec3:26a2]:62586",
"addrlocal": "[2001:0:9d38:6ab8:1475:33eb:adb6:5387]:16662",
"services": "0000000000000001",
"lastsend": 1477775751,
"lastrecv": 1477775751,
"bytessent": 27906,
"bytesrecv": 28079,
"conntime": 1477772118,
"pingtime": 0.188039,
"version": 60800,
"subver": "Silk Core:1.0.1.1",
"inbound": true,
"startingheight": 57911,
"banscore": 0,
"synced_headers": 57975,
"synced_blocks": -1,
"inflight": [
],
"whitelisted": false
}
] |
|
|
|
|
ttoroie -
I see that you have a SLK donation address in your signature. Why not register your name by using the wallet and accept SLK by using ttoroie instead?
Go to DNS in your wallet
enter your name
duration of service
preferred value (much like an address label i.e. receivables)
enter your SLK address if you want to connect your name to an existing address
and hit submit
for a fee of 0.01 SLK/day you can now use your name and your slk address to receive donations.
|
|
|
|
Hello, I have a clean installation of silk-core ( https://github.com/SilkNetwork/Silk-Core) in a new Ubuntu installation and working fine an its synced with the same block height as the explorer https://slkexplorer.silknetwork.org/I am now stuck with the wallet, where can I find the basic commands? see the address of my wallet or create wallet, encrypt wallet. I know and I used: silk-cli help and silk-cli getwalletinfo but it doesn't say much. And then how to do coin splitting/coin control. All of this with command line please. I have no gui installed. Tnx !! Im not familiar with a linux environment but "help" and "getwalletinfo" are valid commands. |
|
|
|
Guys you'll be laughing now but in the new Silk(SLK) wallet: with all the swapping, transfers from weaver, Bittrex and split coins to stake.... I don't know what is my current Silk(SLK) wallet address I've loads of sending and receiving addresses when I sent coins from weaver after the swap I sent them to an address, but now it has a zero balance I used console command listaddressgroupings and it gave me loads of them addys but none has the right amount from the wallet any ideas?  Menu Bar > File > Receive addresses. It shows a list of all addresses in the wallet |
|
|
|
I have received mine and have my wallet open to stake. Thanks! I have received mine and have my wallet open to stake. Thanks! Strange, I lost sync about 30 minutes after sending the msg to help out and have been stuck at 1758505 since last high. I'll keep trying to get synced Sorry... MCDev Yes, we need a few more stakes from other wallets then all of these that were sent can be confirmed and will begin staking. The chain will be back alive again...just very slow right now. my balance is spendable now, and wallet is up to date at 1758515 It is great to see how you guys pulled together! Bravo  |
|
|
|
|
Show Posts
