No, it's not delisted but they are assholes because they incresed the daily average 50% from 0.2 to 0.3. Sent them a ticket and the answer is commentless..
I think they did this to all coins. Will need some sort of a white paper explaining what we are doing with this coin for people to trust it. In the mean time i will try to keep it listed. 
Topic: $XQN Quotient Takeover #Board Of Community #Asset Fund - page 6. (Read 47002 times)
No, it's not delisted but they are assholes because they incresed the daily average 50% from 0.2 to 0.3. Sent them a ticket and the answer is commentless..
It looks like Xqn was delisted from bittrex.
HDF = Headers First. It is the method that bitcoin versions 0.10+ have used for new clients to sync with the existing network. This system, without HEAVY modifications, simply will not work with PoS enabled blockchains. A number of projects have tried to integrate this feature before...none have successfully done so.
I found it easier just to disable the headers first and switch to blocks only. The other route would be to add the necessary information to the header that is missing.
Being a PoW/PoS coin, when trying to implement the newer BTC codebase, I suspect that there were issues with HDF sync and the PoS block validation?
I wish I understood what that means.
All I can tell you is what I know,... we started with the clean newest BTC core and went from there
integrating all we wanted to see in it.
The Coder did an awesome job doing something that had never been done before.
He had it functioning well in Linux 8 months ago, but gettng it compiled in Windows was the issue.
What I cannot or will not at this time is get into specifics as to the tech or features
we decided to include.
Hope you understand...
Yeah I understand...completely
Many of the newer BTC innovations were designed solely for use with BTC. Porting those innovations over to altcoins, and especially altcoins with a non-proof-of-work base is a nightmare to say the least.
HDF = Headers First. It is the method that bitcoin versions 0.10+ have used for new clients to sync with the existing network. This system, without HEAVY modifications, simply will not work with PoS enabled blockchains. A number of projects have tried to integrate this feature before...none have successfully done so.
Thanks for the explanations and for understanding.
What we have for KORE is good enough to release even if the BTC core is a little outdated.
It will still be one of the few at the version it is till we move forward with where we want it to go
which is dependent upon some Coders we are trying to get on board and funded.
I like to learn what I can but have also learned to stop asking the Coders 20 questions
for everything I just have never heard before nor get fully,... so I don't distract them.
ask questions dude! I mean, if you (or someone you represent) are paying for work to be done...ask away!
I myself when taking on paid work am never closed off to questions being asked...thats part of the job!
I agree paid or not,... but you are you, and they are them...
Does not mean they are unjustified since they only have so much time.
Plus I have learned to appreciate some very heavily talented Coders might be a bit eccentric
and/or know they must stay in "the zone" if they are to do their work effectively
for the time they can afford to invest to get done what they need to.
I have also been privileged to learn what a Coder must do and go through
by a highly talented and respected lone wolf Coder.
Not to say I dont have my own issues...
Understood.
Just throwing out my own opinion having been in a situation where someone was paying me to do coding work for them. Sure, there are times where writing code needs NO interruption at all and any interruptions can really screw with forward progress. But, at the same time, I at least always provide an alternative means of communication that is not real-time (ie, email) that someone can send messages to in the "heat of the moment" and they will be seen at an appropriate time.
All this being said, I fully understand that you (and any unnamed powers that be) are working to get things in order. That is of the utmost priority and the details of how that is being done come secondary.
I'm glad to engage with a "project lead" (pardon my reassignment of termonology here, but a "developer" you are not by your own admission...which is perfectly OK) that understands and accepts the semantics and the hardships that come with being a freelance programmer. If there is anything that I can assist with, do let me know (I don't work for "free", but my prices are VERY competitive (depending on what you need, of course)
You are correct and I fully accept that I do not fit the title "Developer" in the coding sense of the term.
If not that could seriously damage a project or Team.
We have attracted some really decent awesome people with varying skill sets and
I think most or all agree that we work well together each doing what we do best
and overlapping where and when needed trying not to cause too much damage and the most benefit.
We decided to allow delays to the projects than align ourselves with unscrupulous people.
RE: "working to provide an alternative to the norm in the crypto space" which is a goal of ours
and yet still we are compiling some interesting stories,...lol.
I find it interesting how an opportunity to make 100 or 1,000+ fold is thrown away for their short term whims
denoting the obvious, it is way more varied and complicated than that...
Crowetic and Teams have been an awesome, capable, balanced person/Teams to align ourselves with.
He has enough various coding experience putting him in the ideal place to deal directly with the Coders.
I enjoyed our conversation and appreciate the offer you have extended.
I will be running it by Crowetic/Team and send you a PM
and link to our slack like chat where the instructions are for a secure VoIP
where we three could have a meet and greet etc.
We do our best to never discuss specifics here or on other platforms that are not ours.
Being a PoW/PoS coin, when trying to implement the newer BTC codebase, I suspect that there were issues with HDF sync and the PoS block validation?
I wish I understood what that means.
All I can tell you is what I know,... we started with the clean newest BTC core and went from there
integrating all we wanted to see in it.
The Coder did an awesome job doing something that had never been done before.
He had it functioning well in Linux 8 months ago, but gettng it compiled in Windows was the issue.
What I cannot or will not at this time is get into specifics as to the tech or features
we decided to include.
Hope you understand...
Yeah I understand...completely
Many of the newer BTC innovations were designed solely for use with BTC. Porting those innovations over to altcoins, and especially altcoins with a non-proof-of-work base is a nightmare to say the least.
HDF = Headers First. It is the method that bitcoin versions 0.10+ have used for new clients to sync with the existing network. This system, without HEAVY modifications, simply will not work with PoS enabled blockchains. A number of projects have tried to integrate this feature before...none have successfully done so.
Thanks for the explanations and for understanding.
What we have for KORE is good enough to release even if the BTC core is a little outdated.
It will still be one of the few at the version it is till we move forward with where we want it to go
which is dependent upon some Coders we are trying to get on board and funded.
I like to learn what I can but have also learned to stop asking the Coders 20 questions
for everything I just have never heard before nor get fully,... so I don't distract them.
ask questions dude! I mean, if you (or someone you represent) are paying for work to be done...ask away!
I myself when taking on paid work am never closed off to questions being asked...thats part of the job!
I agree paid or not,... but you are you, and they are them...
Does not mean they are unjustified since they only have so much time.
Plus I have learned to appreciate some very heavily talented Coders might be a bit eccentric
and/or know they must stay in "the zone" if they are to do their work effectively
for the time they can afford to invest to get done what they need to.
I have also been privileged to learn what a Coder must do and go through
by a highly talented and respected lone wolf Coder.
Not to say I dont have my own issues...
Understood.
Just throwing out my own opinion having been in a situation where someone was paying me to do coding work for them. Sure, there are times where writing code needs NO interruption at all and any interruptions can really screw with forward progress. But, at the same time, I at least always provide an alternative means of communication that is not real-time (ie, email) that someone can send messages to in the "heat of the moment" and they will be seen at an appropriate time.
All this being said, I fully understand that you (and any unnamed powers that be) are working to get things in order. That is of the utmost priority and the details of how that is being done come secondary.
I'm glad to engage with a "project lead" (pardon my reassignment of termonology here, but a "developer" you are not by your own admission...which is perfectly OK) that understands and accepts the semantics and the hardships that come with being a freelance programmer. If there is anything that I can assist with, do let me know (I don't work for "free", but my prices are VERY competitive (depending on what you need, of course)
Being a PoW/PoS coin, when trying to implement the newer BTC codebase, I suspect that there were issues with HDF sync and the PoS block validation?
I wish I understood what that means.
All I can tell you is what I know,... we started with the clean newest BTC core and went from there
integrating all we wanted to see in it.
The Coder did an awesome job doing something that had never been done before.
He had it functioning well in Linux 8 months ago, but gettng it compiled in Windows was the issue.
What I cannot or will not at this time is get into specifics as to the tech or features
we decided to include.
Hope you understand...
Yeah I understand...completely
Many of the newer BTC innovations were designed solely for use with BTC. Porting those innovations over to altcoins, and especially altcoins with a non-proof-of-work base is a nightmare to say the least.
HDF = Headers First. It is the method that bitcoin versions 0.10+ have used for new clients to sync with the existing network. This system, without HEAVY modifications, simply will not work with PoS enabled blockchains. A number of projects have tried to integrate this feature before...none have successfully done so.
Thanks for the explanations and for understanding.
What we have for KORE is good enough to release even if the BTC core is a little outdated.
It will still be one of the few at the version it is till we move forward with where we want it to go
which is dependent upon some Coders we are trying to get on board and funded.
I like to learn what I can but have also learned to stop asking the Coders 20 questions
for everything I just have never heard before nor get fully,... so I don't distract them.
ask questions dude! I mean, if you (or someone you represent) are paying for work to be done...ask away!
I myself when taking on paid work am never closed off to questions being asked...thats part of the job!
I agree paid or not,... but you are you, and they are them...
Does not mean they are unjustified since they only have so much time.
Plus I have learned to appreciate some very heavily talented Coders might be a bit eccentric
and/or know they must stay in "the zone" if they are to do their work effectively
for the time they can afford to invest to get done what they need to.
I have also been privileged to learn what a Coder must do and go through
by a highly talented and respected lone wolf Coder.
Not to say I dont have my own issues...
Being a PoW/PoS coin, when trying to implement the newer BTC codebase, I suspect that there were issues with HDF sync and the PoS block validation?
I wish I understood what that means.
All I can tell you is what I know,... we started with the clean newest BTC core and went from there
integrating all we wanted to see in it.
The Coder did an awesome job doing something that had never been done before.
He had it functioning well in Linux 8 months ago, but gettng it compiled in Windows was the issue.
What I cannot or will not at this time is get into specifics as to the tech or features
we decided to include.
Hope you understand...
Yeah I understand...completely
Many of the newer BTC innovations were designed solely for use with BTC. Porting those innovations over to altcoins, and especially altcoins with a non-proof-of-work base is a nightmare to say the least.
HDF = Headers First. It is the method that bitcoin versions 0.10+ have used for new clients to sync with the existing network. This system, without HEAVY modifications, simply will not work with PoS enabled blockchains. A number of projects have tried to integrate this feature before...none have successfully done so.
Thanks for the explanations and for understanding.
What we have for KORE is good enough to release even if the BTC core is a little outdated.
It will still be one of the few at the version it is till we move forward with where we want it to go
which is dependent upon some Coders we are trying to get on board and funded.
I like to learn what I can but have also learned to stop asking the Coders 20 questions
for everything I just have never heard before nor get fully,... so I don't distract them.
ask questions dude! I mean, if you (or someone you represent) are paying for work to be done...ask away!
I myself when taking on paid work am never closed off to questions being asked...thats part of the job!
Being a PoW/PoS coin, when trying to implement the newer BTC codebase, I suspect that there were issues with HDF sync and the PoS block validation?
I wish I understood what that means.
All I can tell you is what I know,... we started with the clean newest BTC core and went from there
integrating all we wanted to see in it.
The Coder did an awesome job doing something that had never been done before.
He had it functioning well in Linux 8 months ago, but gettng it compiled in Windows was the issue.
What I cannot or will not at this time is get into specifics as to the tech or features
we decided to include.
Hope you understand...
Yeah I understand...completely
Many of the newer BTC innovations were designed solely for use with BTC. Porting those innovations over to altcoins, and especially altcoins with a non-proof-of-work base is a nightmare to say the least.
HDF = Headers First. It is the method that bitcoin versions 0.10+ have used for new clients to sync with the existing network. This system, without HEAVY modifications, simply will not work with PoS enabled blockchains. A number of projects have tried to integrate this feature before...none have successfully done so.
Thanks for the explanations and for understanding.
What we have for KORE is good enough to release even if the BTC core is a little outdated.
It will still be one of the few at the version it is till we move forward with where we want it to go
which is dependent upon some Coders we are trying to get on board and funded.
I like to learn what I can but have also learned to stop asking the Coders 20 questions
for everything I just have never heard before nor get fully,... so I don't distract them.
Being a PoW/PoS coin, when trying to implement the newer BTC codebase, I suspect that there were issues with HDF sync and the PoS block validation?
I wish I understood what that means.
All I can tell you is what I know,... we started with the clean newest BTC core and went from there
integrating all we wanted to see in it.
The Coder did an awesome job doing something that had never been done before.
He had it functioning well in Linux 8 months ago, but gettng it compiled in Windows was the issue.
What I cannot or will not at this time is get into specifics as to the tech or features
we decided to include.
Hope you understand...
Yeah I understand...completely
Many of the newer BTC innovations were designed solely for use with BTC. Porting those innovations over to altcoins, and especially altcoins with a non-proof-of-work base is a nightmare to say the least.
HDF = Headers First. It is the method that bitcoin versions 0.10+ have used for new clients to sync with the existing network. This system, without HEAVY modifications, simply will not work with PoS enabled blockchains. A number of projects have tried to integrate this feature before...none have successfully done so.
Being a PoW/PoS coin, when trying to implement the newer BTC codebase, I suspect that there were issues with HDF sync and the PoS block validation?
I wish I understood what that means.
All I can tell you is what I know,... we started with the clean newest BTC core and went from there
integrating all we wanted to see in it.
The Coder did an awesome job doing something that had never been done before.
He had it functioning well in Linux 8 months ago, but gettng it compiled in Windows was the issue.
What I cannot or will not at this time is get into specifics as to the tech or features
we decided to include.
Hope you understand...
Being a PoW/PoS coin, when trying to implement the newer BTC codebase, I suspect that there were issues with HDF sync and the PoS block validation?
There are big plans for XQN and those here and who support XQN in the future will be very pleased with
where it is being taken.
We do appreciate all offers of help, suggestions and if any would like to join the Core Team.
There is always a need for Honorable Coders but unfortunately it is a widely known but rarely spoken truth that they are a rarity among the alt communities
and finding one is like finding a needle in a haystack.
MM
where it is being taken.
We do appreciate all offers of help, suggestions and if any would like to join the Core Team.
There is always a need for Honorable Coders but unfortunately it is a widely known but rarely spoken truth that they are a rarity among the alt communities
and finding one is like finding a needle in a haystack.
MM
eh...finding honorable coders isn't so much a rarity in and of itself. finding honorable coders that are still doing work for free, however, is indeed a rarity. With an overwhelming number of coins being released where the "Dev" (quoted because 9/10 times the person leading the project hasn't the faintest idea of what is going on with the c++ code and couldn't program a "Hello World" application to save his life) is only looking to make a quick buck, there really is little incentive left that can pull in qualified programmers to make the necessary updates to the (often) sorely outdated codebase.
For reference, one of the failed checks listed in my script output was fixed in bitcoin nearly 2 years ago, yet 90% of new coins haven't applied the patch. Another was patched some 11 months ago, and again...most "new" coins haven't the faintest idea what that vulnerability is.
At least this particular coin has done away with IRC based peer fetching...that was SO 2012!
Unfortunately, with no hex-encoded peer addresses, and a non-functioning DNS seeder, there are some basic connectivity issues that need to be resolved first and foremost (addnodes in a conf file really shouldn't be necessary nor "standard practice").I admit I am one who has no coding experience, has the desire but no time to learn Code since there are far more important matters at hand
in all the projects we have in play.
These have nothing to do with a balanced honorable Coder able to function in a Team atmosphere or
as a lone wolf.
I disagree with you on the honorable part as most Coders free or paid cannot answer the simple question
that if they were approached with a suitcase full of unmarked bills numbering in the hundreds of million of dollars,...
would they take it or not.
With our KORE Coin updates we decided the only right way was to start with the newest Bitcoin Code
and go from there but some snags now have delayed the release nearly 8 months and there have been numerous
updates to the Bitcoin core since then.
This paid honorable Coder has run into some serious life problems and could not continue with
the project so we had the need to replace them.
Bittrex removing GLOBAL and not relisting it even after we got her running again
had put a serious damper on our ability to fund and move forward with our planned releases.
XQN will also be done right surpassing any mere updates to old outdated code.
Most all suggestions of updates and PoS issues will be resolved with where we are taking
our projects.
PS
The little I have messed with changing existing Code and playing around with some changes in a copy paste manner
to have it do what I wanted to, have surpassed what part time coders have been able to do...
I have the utmost respect for Coders and what they are able to do.
This would be a fitting time to mention most honorable Coders and people had been taken for a ride so many times with all the scam
coins that many vowed never to help again or left the alt space and even Crypto Currency entirely...
What we are bringing to this space is a different approach and in time albeit way too much time, we will prove ourselves.
Those who had taken the chance to trust us, join the Core Teams, sign the NDA doxing themselves can attest to this.
We had not said much but that is slowly changing.
There are big plans for XQN and those here and who support XQN in the future will be very pleased with
where it is being taken.
We do appreciate all offers of help, suggestions and if any would like to join the Core Team.
There is always a need for Honorable Coders but unfortunately it is a widely known but rarely spoken truth that they are a rarity among the alt communities
and finding one is like finding a needle in a haystack.
MM
where it is being taken.
We do appreciate all offers of help, suggestions and if any would like to join the Core Team.
There is always a need for Honorable Coders but unfortunately it is a widely known but rarely spoken truth that they are a rarity among the alt communities
and finding one is like finding a needle in a haystack.
MM
eh...finding honorable coders isn't so much a rarity in and of itself. finding honorable coders that are still doing work for free, however, is indeed a rarity. With an overwhelming number of coins being released where the "Dev" (quoted because 9/10 times the person leading the project hasn't the faintest idea of what is going on with the c++ code and couldn't program a "Hello World" application to save his life) is only looking to make a quick buck, there really is little incentive left that can pull in qualified programmers to make the necessary updates to the (often) sorely outdated codebase.
For reference, one of the failed checks listed in my script output was fixed in bitcoin nearly 2 years ago, yet 90% of new coins haven't applied the patch. Another was patched some 11 months ago, and again...most "new" coins haven't the faintest idea what that vulnerability is.
At least this particular coin has done away with IRC based peer fetching...that was SO 2012!
Unfortunately, with no hex-encoded peer addresses, and a non-functioning DNS seeder, there are some basic connectivity issues that need to be resolved first and foremost (addnodes in a conf file really shouldn't be necessary nor "standard practice"). Where should we start? The wallet works and is ok for now. I do think it needs something special. How can quotient differentiate itself from other coins?
how about making some updates to the wallet's source code to include recent checkpoints, better (read: "working") default connection nodes, update support for more recent supporting library versions, and patch up a pretty serious vulnerability in the PoS system?
Code:
___ _ ___ _ _
/ __\___ (_)_ __ / __\ |__ ___ ___| | _____ _ __
/ / / _ \| | '_ \ / / | '_ \ / _ \/ __| |/ / _ \ '__|
/ /__| (_) | | | | / /___| | | | __/ (__| < __/ |
\____/\___/|_|_| |_\____/|_| |_|\___|\___|_|\_\___|_|
v0.0.3 September 2016 | http://www.fuzzbawls.pw
Creating temp folder to clone remote repository...
Cloning https://github.com/CedricProfit/Quotient.git...
-= Repository Information =-
============================================================
Number of commits: 18
Last commit date: Sun, Jan 18, 2015 11:06:17 PM
Days since last commit: 619.70 Days
-= Build System Information =-
============================================================
Build Type: QMAKE/Makefile
Build Version: 1.1.1.0
Qt Bin: quotient-qt
Daemon Bin: quotientd
OS X Icon: bitcoin.icns
-= Coin Specifications =-
============================================================
Coin Name: quotient
Client Version: 1.6.1.17
Client Name: /ProfitReaper:1.6.1.17/
Default P2P Port: 30994
Default PRC Port: 30997
-= Coin Information Checks =-
============================================================
Matching P2PPORT in init documentation: [!!]
Matching RPCPORT in init documentation: [!!]
Build & Client Version Match: [!!]
-= Library Version Compliance Checks =-
============================================================
Miniupnpc v1.9 (API 14): [!!]
OpenSSL v1.0.1k+ (Strict DER Signatures): [!!]
Boost v1.58+ (boost::get): [OK]
-= Security Standards Checks =-
============================================================
Free of IRC related files: [OK]
IRC based peer fetching: [--]
Contains signature malleability patch (PPCoin): [!!]
-= Connectivity Checks =-
============================================================
Contains unique ClientName: [OK]
Contains DNS seeder addresses: [OK]
Contains Hex-Encoded seeder addresses: [!!]
Has at least ONE default connection method: [OK]
Number of DNS Seeds: 1
Listing DNS Seed addresses...
* seed.quotientcoin.com
* Address Unresolved!
-= OS Specific Checks =-
============================================================
Mac OS X Native Notification Support: [OK]
Mac OS X Deployment Script: [OK]
Mac OS X Application Icon: [OK]
Windows Deployment Script: [**]
============================================================
* Windows deployment script is using an incorrect name!
* Deployment build won't have the correct metadata!
* Windows deployment sript is using an incorrect version!
* Deployment build won't have the correct metadata!
Results should be manually verified and you should NOT rely
on any automated scripts (including this one) before running
or compiling any crypto wallet.
============================================================
There are big plans for XQN and those here and who support XQN in the future will be very pleased with
where it is being taken.
We do appreciate all offers of help, suggestions and if any would like to join the Core Team.
There is always a need for Honorable Coders but unfortunately it is a widely known but rarely spoken truth that they are a rarity among the alt communities
and finding one is like finding a needle in a haystack.
MM
Where should we start? The wallet works and is ok for now. I do think it needs something special. How can quotient differentiate itself from other coins?
how about making some updates to the wallet's source code to include recent checkpoints, better (read: "working") default connection nodes, update support for more recent supporting library versions, and patch up a pretty serious vulnerability in the PoS system?
Code:
___ _ ___ _ _
/ __\___ (_)_ __ / __\ |__ ___ ___| | _____ _ __
/ / / _ \| | '_ \ / / | '_ \ / _ \/ __| |/ / _ \ '__|
/ /__| (_) | | | | / /___| | | | __/ (__| < __/ |
\____/\___/|_|_| |_\____/|_| |_|\___|\___|_|\_\___|_|
v0.0.3 September 2016 | http://www.fuzzbawls.pw
Creating temp folder to clone remote repository...
Cloning https://github.com/CedricProfit/Quotient.git...
-= Repository Information =-
============================================================
Number of commits: 18
Last commit date: Sun, Jan 18, 2015 11:06:17 PM
Days since last commit: 619.70 Days
-= Build System Information =-
============================================================
Build Type: QMAKE/Makefile
Build Version: 1.1.1.0
Qt Bin: quotient-qt
Daemon Bin: quotientd
OS X Icon: bitcoin.icns
-= Coin Specifications =-
============================================================
Coin Name: quotient
Client Version: 1.6.1.17
Client Name: /ProfitReaper:1.6.1.17/
Default P2P Port: 30994
Default PRC Port: 30997
-= Coin Information Checks =-
============================================================
Matching P2PPORT in init documentation: [!!]
Matching RPCPORT in init documentation: [!!]
Build & Client Version Match: [!!]
-= Library Version Compliance Checks =-
============================================================
Miniupnpc v1.9 (API 14): [!!]
OpenSSL v1.0.1k+ (Strict DER Signatures): [!!]
Boost v1.58+ (boost::get): [OK]
-= Security Standards Checks =-
============================================================
Free of IRC related files: [OK]
IRC based peer fetching: [--]
Contains signature malleability patch (PPCoin): [!!]
-= Connectivity Checks =-
============================================================
Contains unique ClientName: [OK]
Contains DNS seeder addresses: [OK]
Contains Hex-Encoded seeder addresses: [!!]
Has at least ONE default connection method: [OK]
Number of DNS Seeds: 1
Listing DNS Seed addresses...
* seed.quotientcoin.com
* Address Unresolved!
-= OS Specific Checks =-
============================================================
Mac OS X Native Notification Support: [OK]
Mac OS X Deployment Script: [OK]
Mac OS X Application Icon: [OK]
Windows Deployment Script: [**]
============================================================
* Windows deployment script is using an incorrect name!
* Deployment build won't have the correct metadata!
* Windows deployment sript is using an incorrect version!
* Deployment build won't have the correct metadata!
Results should be manually verified and you should NOT rely
on any automated scripts (including this one) before running
or compiling any crypto wallet.
============================================================
If they put it back up I will make sure to keep volume up over 1.4. I have been keeping my coins in the wallet and not selling or buying. I can change this by buying and selling at times.
I have also sold some xqn for the volume but we need about 1 btc at least for a day to be near the1.4Btc that is required for 7 days. hope that mike and crow could talk them out of delisting the teams coins.
I bought all I could afford on the open market.
Looks like we still need about .075BTC in volume.
I would have much rather this money go to paying Coders for work...
I have contacted Bittrex once again concerning the legitimacy of all our coins and projects and to keep them listed.
I could understand there are the scammers and etc but there are also legitimate projects as ours that have
had a huge uphill battle and we are still forging ahead.
Shame one of those battles is Bittrex auto delisting program which has already cost us much pain, delay and money
plus has limited our ability to fund our projects by delisting a pivotal coin/GLOBAL they were made aware of prior to it being delisted.
Now they want an exorbitant fee to relist so we have had to reorganize a number of our priorities and our projects.
I have always been in contact with Bittrex to not delist our projects coins and yet they still delist.
I presume this is an automated process but what I do not understand is why they are not immediately relisted.
We have hundreds and even thousands of hours and dollars spent on these projects behind the scenes
and are deliberately keeping things quiet and consistently tell Bittrex this.
It takes time to build teams with quality people, Coders and mainly self fund the work.
I do hope there could be an arrangement for those honest projects and Teams such as ours
that they could take our projects out of that auto delisting program till projects either come through
or I could see the combining of coins/projects into one. In otherwords, till we ask them to...
Most Sincerely,
MikeMike
I hope Bittrex could make yet another section for their coins rather than just a low liquidity one.
For coins and projects such as ours that we deliberately do not P&D nor hype with bling etc.
An "under development/takeover" section that we must communicate with them every 3 months or something like that.
Maybe have a requirement that ID be presented to enter this section...
The "under maintenance" lines up with the delisting date.
Maybe they are holding it "in maintenance mode" till we have our meeting with them.
Bittrex knows I am tied to the XQN development.
My wallet is functioning properly and they have not notified me of any issues with the wallet.
I have also sold some xqn for the volume but we need about 1 btc at least for a day to be near the1.4Btc that is required for 7 days. hope that mike and crow could talk them out of delisting the teams coins.
I bought all I could afford on the open market.
Looks like we still need about .075BTC in volume.
I would have much rather this money go to paying Coders for work...
I have contacted Bittrex once again concerning the legitimacy of all our coins and projects and to keep them listed.
I could understand there are the scammers and etc but there are also legitimate projects as ours that have
had a huge uphill battle and we are still forging ahead.
Shame one of those battles is Bittrex auto delisting program which has already cost us much pain, delay and money
plus has limited our ability to fund our projects by delisting a pivotal coin/GLOBAL they were made aware of prior to it being delisted.
Now they want an exorbitant fee to relist so we have had to reorganize a number of our priorities and our projects.
I have always been in contact with Bittrex to not delist our projects coins and yet they still delist.
I presume this is an automated process but what I do not understand is why they are not immediately relisted.
We have hundreds and even thousands of hours and dollars spent on these projects behind the scenes
and are deliberately keeping things quiet and consistently tell Bittrex this.
It takes time to build teams with quality people, Coders and mainly self fund the work.
I do hope there could be an arrangement for those honest projects and Teams such as ours
that they could take our projects out of that auto delisting program till projects either come through
or I could see the combining of coins/projects into one. In otherwords, till we ask them to...
Most Sincerely,
MikeMike
I have also sold some xqn for the volume but we need about 1 btc at least for a day to be near the1.4Btc that is required for 7 days. hope that mike and crow could talk them out of delisting the teams coins.
I bought all I could afford on the open market.
Looks like we still need about .075BTC in volume.
I would have much rather this money go to paying Coders for work...
I have contacted Bittrex once again concerning the legitimacy of all our coins and projects and to keep them listed.
I could understand there are the scammers and etc but there are also legitimate projects as ours that have
had a huge uphill battle and we are still forging ahead.
Shame one of those battles is Bittrex auto delisting program which has already cost us much pain, delay and money
plus has limited our ability to fund our projects by delisting a pivotal coin/GLOBAL they were made aware of prior to it being delisted.
Now they want an exorbitant fee to relist so we have had to reorganize a number of our priorities and our projects.
I have always been in contact with Bittrex to not delist our projects coins and yet they still delist.
I presume this is an automated process but what I do not understand is why they are not immediately relisted.
We have hundreds and even thousands of hours and dollars spent on these projects behind the scenes
and are deliberately keeping things quiet and consistently tell Bittrex this.
It takes time to build teams with quality people, Coders and mainly self fund the work.
I do hope there could be an arrangement for those honest projects and Teams such as ours
that they could take our projects out of that auto delisting program till projects either come through
or I could see the combining of coins/projects into one. In otherwords, till we ask them to...
Most Sincerely,
MikeMike
Jump to: