 Show Posts
|
|
Pages: [1] 2 3 4 5 6 7 »
|
|
This week's spending report is now available:
Available BTC at the start of the week: 0.23591
Spendings:
CloudOcean’s servers: 0.06799 BTC
Gains:
ICO Funding: 52.3401 BTC
Available BTC at the end of the week: 52.56892
|
|
|
|
|
We are still here and although out policy is to not comment on the market price we can say we haven't "self-bought" our ICO.
|
|
|
|
|
Great news. The new wallet is almost ready, will be available monday. This wallet will solve the problems pool have been having with the algo by changing it to normal scrypt (litecoin, dogecoin).
The fourier protocol implementation is still on track to happen in new years making our last roadmap still valid.
|
|
|
|
C-cex just burned the unsold ICO coins. Their tweet: "WRP ICO leftover coins burned to non-wallet address: a68c87975a7586d8b00d2c6d2ee971629e1f3846590883f9f5fbfb2cd07764f9" In wallet mining look strange, blocksize changes , "hashespersec" : 0 most of the time??
(..)
We are working on getting this fixed but it has to do with lyra2 not being completely backwards compatible. Is there any use in mining then? or are u going to reward me to for finding the bug? We knew about this bug before it has been talked about in our Slack and we said we were correcting ita few posts ago. Mining works and you can find blocks normally. |
|
|
|
C-cex just burned the unsold ICO coins. Their tweet: "WRP ICO leftover coins burned to non-wallet address: a68c87975a7586d8b00d2c6d2ee971629e1f3846590883f9f5fbfb2cd07764f9" In wallet mining look strange, blocksize changes , "hashespersec" : 0 most of the time??
(..)
We are working on getting this fixed but it has to do with lyra2 not being completely backwards compatible. |
|
|
|
|
We are still waiting for you to burn the coins you said you would burn 24 hours ago.
|
|
|
|
How does one mine from the wallet? pardon my ignorance.
While no pools are available you can use the in wallet miner. We have been talking to pools and they had sone difficulties with the algo. We will present a solution for this in a few days. |
|
|
|
Is there a blockexplorer for wrapper?
Coming this friday. Already contacted the guys at chainz. Btw, if you are not on our Slack you probably don't know this, the guys at c-cex still didn't burn our coins after we extensively asked them too. We are pressuring them again tomorrow. The question is: how can you really pressure them? We've been calling them publicly by sending them daily tweets. Also been talking to them via skype. |
|
|
|
Is there a blockexplorer for wrapper?
Coming this friday. Already contacted the guys at chainz. Btw, if you are not on our Slack you probably don't know this, the guys at c-cex still didn't burn our coins after we extensively asked them too. We are pressuring them again tomorrow. |
|
|
|
We also have a roadmap, in case anyone missed it:  |
|
|
|
|
As the name suggests, this is the first version of the whitepaper. English is not our first language as well but we will contact a native speaker to go over the writing.
And maybe we should make the whitepaper a little more visible in the OP, seems like a big part of the people that read it don't notice we have one.
EDIT: It's being done right now.
|
|
|
|
Not sure what is new in the ico coin. Sounds like zerocoin is just ported from coins like zcoin. Anything technically new and implemented?
We are working on something we call "Fourier Protocol", it's being worked in the dev branch and you can read more about it in the OP, our website or our whitepaper. |
|
|
|
yah cucks its so fucking hard to comprehend that the "dev" posting in here is not the actual dev. keep supporting this rubbish
What is your problem? If you have questions "the team" responds asap in the slack? I've been in the slack since day 1 and haven't seen any questions go unanswered. I do. I have a Giza-sized bunch of questions. All about i2p relay. I didnt know there was a slack channel. Anyways Im not hanging on in there. I will unlikely join. Better have him (the person allegedly developing the claimed in the OP tech) release the whitepaper, it will be my pleasure to read up on it. I still think he hasnt got enough technical savvy to do a paper. This tech is one of the most promising technologies being worked on in telecommunications and computer networks as of now. Sadly, its not gonna go along with the draft proposed in the OP and dev's commitment to it. There you go: http://wrapperproject.com/wp-content/uploads/2016/11/WrapperWhitepaper1_0.pdf |
|
|
|
|
We are aware of problems with the "getnetworkhashps" function and are working on it. We are also hiring another developer soon so we can speed things a bit in the development end.
|
|
|
|
Great news! We are successfully past block 500 and are now running lyra2. Difficulty is adjusting.
Are you going to release a new wallet? The current one is still running Scrypt for the built-in miner. Do you guys even know what you're doing?  Yes we do. Take a look at our main.cpp here: https://github.com/wrapperproject/wrapper/blob/0cb1a4ea53b50b0c056be525fecd4551de94142b/src/main.cppPlease read line 6258. The debug.log will show a message saying it's running a scrypt miner even when lyra2 is running (line 6293). Thank you for bringing this to our attention. We will fix it now. We have been test mining here without difficulties. Great news! We are successfully past block 500 and are now running lyra2. Difficulty is adjusting.
The weird thing is that now the blocks are being found quicker than before. I would expect less blocks with the new algo (which now I don't know if it's the same as the zcoin or what) Difficulty is still adjusting but it should settle in 12 minutes soon. |
|
|
|
|
Great news! We are successfully past block 500 and are now running lyra2. Difficulty is adjusting.
|
|
|
|
Can we get the actual dev to join the convo to add some transparency to the project. I think what some people are saying because of how your the Middle man and it's pretty obvious that you didn't actually develop the coin and had someone clone another project for you to base off of. Maybe a little more transparency to the public is in order. Usually Devs have no issues jumping in on a convo. This way you can put and did to rest.
What are the questions people have? We are a team and my job is to moderate and answer investors doubts and concerns, the developer who is currently working on the Fourier Protocol and that cloned Wrapper is not a random person we hired, he's with us and is part of the project. We have a strict roadmap we are following and have been delivering and building upon it since the beggining (even before the ICO launched), if there are concerns please explain them directly here, via Slack or via PM and I'll answer them ASAP. |
|
|
|
their wallet is full of viruses and they're not false positives due to the miner.
these guys paid some dodgy developer to do that wallet for them.
We have addressed that. The wallet was compile by us and the positives are due to our in-wallet miner. Its main focus is to bring the power of i2p to the masses. i2p! This is internet 5.0. Why would u waste time on an in-wallet miner when u develop such an important tech as i2p? We did not develop I2P and our main focus isn't to bring I2P to the masses. I'm not sure where you got that information from. |
|
|
|
I was raped by the dev. My dark hole still hurts from his fat ebola belly. Please guys, don't ever buy this again.
Your feedback is noted, but from this point on we'll only respond to constructive dialogue. |
|
|
|
their wallet is full of viruses and they're not false positives due to the miner.
these guys paid some dodgy developer to do that wallet for them.
We have addressed that. The wallet was compile by us and the positives are due to our in-wallet miner. |
|
|
|
|
