Author

Topic: [XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 190. (Read 804700 times)

full member
Activity: 178
Merit: 100
LiskHQ CTO
CryptiKit Update - Simple & easy Crypti node deployment and management.

Hello Everyone Smiley. I'm pleased to announce yet another update to CryptiKit! I will keep rolling these out as this is how I prefer to release.

This release brings a major performance workaround to the check_nodes task. Additionally, CryptiKit can now deploy Crypti nodes to CentOS (7.0 x64) and Fedora (20 x64) operating systems on supported hosts. Be sure to read the Changelog.md and README.md for usage instructions.

I also want to give a BIG shout out to PabloAngello and Barie on the #CryptiTalk IRC for their valuable suggestions and words of encouragement. Without which I would have given up a long time ago...

Please download here: https://github.com/karmacoma/cryptikit/releases/tag/v1.7.0

If you don't know about CryptiKit and what it can do already, please read here:
- https://github.com/karmacoma/cryptikit/blob/v1.7.0/README.md



Changelog

  • Adding support for deployment to CentOS and Fedora operating systems

For usage instructions please see:
https://github.com/karmacoma/cryptikit/blob/v1.7.0/README.md#typical-usage

For available operating systems for each supported host please see:
https://github.com/karmacoma/cryptikit/blob/v1.7.0/README.md#supported-hosts

  • Implementing workaround for slow check_nodes task

Forging status is now checked separately from mining info; Allowing slow /api/getMiningInfo requests to be optionally avoided. Mining info can therefore be disabled permanently through config.yml or optionally at runtime from the command line.

For more information please see:
https://github.com/karmacoma/cryptikit/blob/v1.7.0/README.md#mining-info

  • Downloading zip files to static file names; Allowing app and blockchain urls to be more easily customised without breaking CryptiKit

Example config.yml with customised URLs hosted on Dropbox:

Code:
app_url: https://www.dropbox.com/s/ygjs6wwukj3h3ho/crypti-linux-0.1.7.zip?dl=0
blockchain_url: https://www.dropbox.com/s/rbkx0rtvhp4xxbe/blockchain.db.zip?dl=0



Cheers, Smiley Karmacoma24.
hero member
Activity: 511
Merit: 500
Boris, Crypti Lead Developer, Lisk Advisor
Whats the progress on the Polo deposits, if any?

As i wrote before i got only it from polo:

>> It's working.

I sent few messages on last week and on this week.
Waiting for result.

I checked, my transaction was on polo but without confirmations.
I sent instruction how try to fix it.

What a joke. One side is in full skullduggery mode. Which is it? Why is it such an issue when other exchanges have it working fine? I have about 800k xcr locked up there (lost?). I wonder how many others and how much xcr is locked up there. Were bouncing back and forth with this blame game nonsense. My guess is polo screwed their wallet and the funds are gone. This has literally been going on for MONTHS! I suggest everyone who has xcr locked up at polo post in here stating so, to get the start of a head count. Then organize to barrage their support with demands to fix the issue (or fess up or do whatever it is they need to do to make it right). This is unacceptable.

What i can do? If they didn't sent me answer from last friday?
I sent all what i can to polo. Other exchanges usually works good, yes.
But this is stupid situation with polo.
hero member
Activity: 511
Merit: 500
Boris, Crypti Lead Developer, Lisk Advisor
Whats the progress on the Polo deposits, if any?

As i wrote before i got only it from polo:

>> It's working.

I sent few messages on last week and on this week.
Waiting for result.

I checked, my transaction was on polo but without confirmations.
I sent instruction how try to fix it.
hero member
Activity: 511
Merit: 500
Boris, Crypti Lead Developer, Lisk Advisor
Dev,Wallet launch plan, what time?

We will make new roadmap with announced in GreXX blog functional.
Now all in developing, maybe later i will share trello for all to see progress.
member
Activity: 165
Merit: 10
Dev,Wallet launch plan, what time?
No plan dump your coins
Go ahead. Cheesy

looks like the majority of weak hands have sold.. But it's just one day.. Although there are some larger buy walls up which is encouraging.
Regards,
Brian
Most buy in 400 sat around will dump later Roll Eyes
So bag holders wait for my dump Wink
heh, bought  lots at 400, not thinking about dumping yet Tongue
sr. member
Activity: 280
Merit: 250
Dev,Wallet launch plan, what time?
No plan dump your coins
Go ahead. Cheesy

looks like the majority of weak hands have sold.. But it's just one day.. Although there are some larger buy walls up which is encouraging.
Regards,
Brian
Most buy in 400 sat around will dump later Roll Eyes
So bag holders wait for my dump Wink
legendary
Activity: 1121
Merit: 1003
Dev,Wallet launch plan, what time?
No plan dump your coins
Go ahead. Cheesy

looks like the majority of weak hands have sold.. But it's just one day.. Although there are some larger buy walls up which is encouraging.
Regards,
Brian
sr. member
Activity: 280
Merit: 250
Dev,Wallet launch plan, what time?
No plan dump your coins
Go ahead. Cheesy
sr. member
Activity: 364
Merit: 250
Stand up , Stand up , Stand up !
Dev,Wallet launch plan, what time?
full member
Activity: 178
Merit: 100
LiskHQ CTO
CryptiKit Update - Simple & easy Crypti node deployment and management.

Hello Everyone Smiley, Another quick but worthwhile update for CryptiKit.
This release fixes an installation issue related to rvm and adds official support for Vultr and Wable cloud hosting providers.

Please download here: https://github.com/karmacoma/cryptikit/releases/tag/v1.6.5

If you don't know about CryptiKit and what it can do already, please read here:
- https://github.com/karmacoma/cryptikit/blob/v1.6.5/README.md



Changelog

  • Officially supporting additional hosts: Vultr and Wable
    • Tested on: Debian 7.0 x64 and Ubuntu 14.04 x64 operating systems
  • Downloading GPG public key before installing or updating rvm

For more information regarding supported hosts see:
https://github.com/karmacoma/cryptikit/blob/v1.6.5/README.md#supported-hosts



Cheers, Smiley Karmacoma24.
hero member
Activity: 518
Merit: 500
Yeah, in reference to Polo. They believed they had it fixed so I personally tested a deposit and it never confirmed with the network. We are trying to get back in touch with them to find out whats happening.
hero member
Activity: 511
Merit: 500
Boris, Crypti Lead Developer, Lisk Advisor
Boris has been working with Polo since the last post where they claimed we were the problem I believe 2 weeks ago maybe now. He has tried to get in touch with their Dev on several occasions but their Dev was not available over the last couple days. Boris provided them direct assistance and custom versions to try and get logs from the Dev. I have no idea what the problem is or why it is such a complicated fix.

Just keep in mind that BTER had the new version up to date in about 5 minutes with no issues whatsoever and has been up and working since. So to say that our network is the problem, to me, seems unlikely as we have users transferring money as well as another exchange transferring funds with no issue interfacing with our network.

I don't know their setup personally and we have witnessed from Wulfs comments that he was having trouble sending with his Windows wallet (I believe?). It could be an isolated strange issue or maybe they are using some kind of unique configuration with a windows wallet that is causing a similar issue to Wulfs. I really can't say.

I wouldn't be quick to lay blame on either of us as it is probably a problem with the unique configuration of their network and site and how it interfaces with our setup that just has some kind of kink in communicating.

TL;DR Boris has been in contact with them whenever they have been available and he has been trying to help them.

Hi Grexx, thanks for the update! This was the latest response a couple of days ago from Poloniex regarding the ticket about XCR I've opened at their site:
I've been waiting on Boris for several days now. He is supposed to send me a special version of XCR with increased logging features. He recently contacted me apologizing for the delay, saying it was due to sickness.

As far as I can see, people are pointing at each other without a real solution...


Answer from Polo on XCR:
Boris provided a custom version, but did not tell me what to do with it. He wants to connect on IRC -- I tell him when I am available, and he never seems to be around. We're in very different timezones. I think we should be emailing because of this, but he said we should do IRC instead. Neither of us know what the issue is right now. At the very least, XCR is not reporting errors correctly, as it claims transactions are being sent but they never make it to the block chain.


Grexx/Boris?

I'm in IRC all my working time. Sometimes i checked #poloniex channel, but i have not seen busoni.

Last what i got from polo dev, it was today night for me:

>> We don't seem to be connecting on IRC.

Today i sent version again with instruction what need to do.
Previous problems with polo, looks like there was problem with their firewall,but i'm not sure.

So basically this issue is deadlocked and no one is doing shit about it so we should kiss our XCR goodbye. Raw deal.

I'm still in contact with polo, wait for news. If IRC not works for this guys, i sent offer to work via Skype.
Maybe after this instruction/version we will see what happening on their servers with Crypti.

Anyway, It's possible to just send money back to senders, just use another node.

Hi Boris,

Can you tell me (us) in conrete steps how to get my funds out of Polo at this moment?

Kind regards.
M.

I'm in contact with polo, yesterday we got first results. I sent fix, working on it. Once all finished i will notify all.

From good news. We finally hired new developer. Starting work on new MVP.

Hi Boris,

Couple of days further... is Polo fixed/functional again in the meanwhile?
What is the status?

M.

Last what i had from polo:

>> It's working

Sent another message on last Friday, and send again just now. Waiting for result.
newbie
Activity: 46
Merit: 0
Boris has been working with Polo since the last post where they claimed we were the problem I believe 2 weeks ago maybe now. He has tried to get in touch with their Dev on several occasions but their Dev was not available over the last couple days. Boris provided them direct assistance and custom versions to try and get logs from the Dev. I have no idea what the problem is or why it is such a complicated fix.

Just keep in mind that BTER had the new version up to date in about 5 minutes with no issues whatsoever and has been up and working since. So to say that our network is the problem, to me, seems unlikely as we have users transferring money as well as another exchange transferring funds with no issue interfacing with our network.

I don't know their setup personally and we have witnessed from Wulfs comments that he was having trouble sending with his Windows wallet (I believe?). It could be an isolated strange issue or maybe they are using some kind of unique configuration with a windows wallet that is causing a similar issue to Wulfs. I really can't say.

I wouldn't be quick to lay blame on either of us as it is probably a problem with the unique configuration of their network and site and how it interfaces with our setup that just has some kind of kink in communicating.

TL;DR Boris has been in contact with them whenever they have been available and he has been trying to help them.

Hi Grexx, thanks for the update! This was the latest response a couple of days ago from Poloniex regarding the ticket about XCR I've opened at their site:
I've been waiting on Boris for several days now. He is supposed to send me a special version of XCR with increased logging features. He recently contacted me apologizing for the delay, saying it was due to sickness.

As far as I can see, people are pointing at each other without a real solution...


Answer from Polo on XCR:
Boris provided a custom version, but did not tell me what to do with it. He wants to connect on IRC -- I tell him when I am available, and he never seems to be around. We're in very different timezones. I think we should be emailing because of this, but he said we should do IRC instead. Neither of us know what the issue is right now. At the very least, XCR is not reporting errors correctly, as it claims transactions are being sent but they never make it to the block chain.


Grexx/Boris?

I'm in IRC all my working time. Sometimes i checked #poloniex channel, but i have not seen busoni.

Last what i got from polo dev, it was today night for me:

>> We don't seem to be connecting on IRC.

Today i sent version again with instruction what need to do.
Previous problems with polo, looks like there was problem with their firewall,but i'm not sure.

So basically this issue is deadlocked and no one is doing shit about it so we should kiss our XCR goodbye. Raw deal.

I'm still in contact with polo, wait for news. If IRC not works for this guys, i sent offer to work via Skype.
Maybe after this instruction/version we will see what happening on their servers with Crypti.

Anyway, It's possible to just send money back to senders, just use another node.

Hi Boris,

Can you tell me (us) in conrete steps how to get my funds out of Polo at this moment?

Kind regards.
M.

I'm in contact with polo, yesterday we got first results. I sent fix, working on it. Once all finished i will notify all.

From good news. We finally hired new developer. Starting work on new MVP.

Hi Boris,

Couple of days further... is Polo fixed/functional again in the meanwhile?
What is the status?

M.
full member
Activity: 178
Merit: 100
LiskHQ CTO
They confirm that they failed to code their own forging algo and will try to use some others - DPoS Roll Eyes
Very disappointing news Cry

Well maybe I am more patient and resilient than you are. From where I am standing, GreXX’s latest blog post is hugely exciting and is a signal to buy more crypti while it is still so cheap.

In summary:

  • The team has accepted the foundation in it’s current form was not working efficiently and therefore will be changed.
  • SyRenity will be now lead the project which will mean more immediate and responsive decision making.
  • New releases with stable and faster performance are coming shortly.
  • The Dev Team have finalized a decision to use a modified version of Delegated Proof of Stake (DPoS) as the new reward system.
  • Custom Block Chains has not been forgotten and is still a top priority for the team.

The Dev Team’s acceptance of failure and the willingness to adapt to an ever changing environment is the main reason why I will continue to support this community in whichever way possible.
legendary
Activity: 1367
Merit: 1000

starik69, did you sell?

Is it the last train to cut losses?
No, i am not selling.  Wink And i am not prophet, think yourself. Tongue
legendary
Activity: 952
Merit: 1000
Yeah! I hate ShroomsKit!
The Way Forward

A new blog post is up at the official Crypti blog. http://blog.crypti.me/the-way-forward/
See nothing but words Shocked
They confirm that they failed to code their own forging algo and will try to use some others - DPoS Roll Eyes
Very disappointing news Cry

starik69, did you sell?

Is it the last train to cut losses?
legendary
Activity: 1367
Merit: 1000
The Way Forward

A new blog post is up at the official Crypti blog. http://blog.crypti.me/the-way-forward/
See nothing but words Shocked
They confirm that they failed to code their own forging algo and will try to use some others - DPoS Roll Eyes
Very disappointing news Cry
full member
Activity: 178
Merit: 100
LiskHQ CTO
CryptiKit Update - Simple & easy Crypti node deployment and management.

Hello Everyone Smiley, New release tag for CryptiKit.
This release fixes a few bugs and adds better handling of bad or non-responsive crypti nodes.

Please download here: https://github.com/karmacoma/cryptikit/releases/tag/v1.6.4

If you don't know about CryptiKit and what it can do already, please read here:
- https://github.com/karmacoma/cryptikit/blob/v1.6.4/README.md



Changelog

  • Copying rather than moving config.yml when updating CryptiKit
  • Escaping forward slash character when saving passphrase to config.json
  • Adding connection and operation timeouts to curl requests
    • 30 seconds until connection to crypti node times out
    • 60 seconds until crypti API query times out
  • Gracefully handling (CTRL+C) user interrupts



Cheers, Smiley Karmacoma24.
sr. member
Activity: 280
Merit: 250
The Way Forward

A new blog post is up at the official Crypti blog. http://blog.crypti.me/the-way-forward/
See nothing but words Shocked
hero member
Activity: 724
Merit: 500
The Way Forward

A new blog post is up at the official Crypti blog. http://blog.crypti.me/the-way-forward/

"shoon" should be "soon" in the first paragraph.
Jump to: