|
FlungSpun
|
 |
June 20, 2014, 06:48:57 PM |
|
Phew. That lot sounds like a not much research ... ooooh butt hurt situation.
Tranz is navigating this coin through a recovery from near oblivion, it's risky but people have voted with their BTC in support of his efforts.
And people who have taken a moment to think it through obviously think its worth the risk to support it.
In other news my wallets are working ship shape after above posted advice on this thread and I'm looking forward to the tranzition on the 4th
to the new chain, may it work flawlessly or get a dose of community support to nudge it along ... but please no more
WORDS
I love mining this coin - it's my my best interest to put my money where my miners are - simple as that. They told me at Mintpal they don't take 'bribes' ...er... I mean Donations. trust me - it's cost me more than 1 btc in lost revenue if I could have sold for 10,000 instead of sitting and playing with myself as I waited for big jerk off vern and his merry band of dysfuncional programmers to get off their asses. I told a friend of mine we'd see 6,000 or close to it when the dump came after they got the wallet working and now we'have to wait a few weeks before things return to normal and there's no guarantee BTC will still be at 600 when the value of CAP recovers from the dump If the deposits hadn't gone down the price would not have spiked the only people losing out there are buying on a coin that cant be deposited and miners blindly following coinwarz etc. First thing I looked at when price started moving again was can I deposit ? No .. right then i'm not mining it OR buying it because the price is unreliable. Cryptsy should really suspend trading when this happens because it has knock on effects for difficulty when there is only one exchange to compare. and the auto exchange feature is probably backed up with all those hopeful souls keen to dump the minings I cant accuse anyone of taking advantage but I wasn't born yesterday either.. So I call myself out of the fray until it looks like I'm playing a fair game again. If you had significant deposit on cryptsy that price would not have happened you only think you saw something happen - it was never really an opportunity in my view, just numbers. In short I agree with you but you walked right into it and shouldnt be complaining in this thread about those issues. The coin is starting to go somewhere again. Are you a supporter or a profiteer? |
|
|
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
jjj0923
|
|
June 20, 2014, 06:53:46 PM |
|
I'll support the coin as long as I deem it profitable to mine.
I have no altruistic intentions.
that said - "what is good for the coin?" - to allow it to languish at 1 satoshi like so many other coins or and have people like me mine it and do everything I can do to drive up it's value...
that's my opinion...
|
|
|
|
Tranz
Legendary
 Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
June 20, 2014, 07:30:18 PM |
|
Since I updated to 2.1 yesterday the wallet is using LOTS of network bandwidth. I let it run over night and this morning it was sending at a rate of nearly 100 kb/s. Perfmon is showing Bottlecaps connections with 5-15 kb/s. Debug log is full of getblocks. Deleting peers.dat and restarting wallet doesn't fix it. What can I do?
So there are still a few people who do not know their wallet is stuck and requesting the same blocks over and over. After the fork I am going to be sending an alert to all people on 2.0 and 2.0.0.1. Advising them to check and make sure they are on the right block and that they should upgrade to 2.1 to fix a staking issue with their client. In the mean time you can click the connections bar and see if you have a bad peer. You can see a bad peer as follows. Good Peer: Peer IP: 176.37.67.61:7685 Time Connected: 18:23:58 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:27:10 2014 Bytes Sent: 795295Bytes Recv: 838737 Blocks Requested: 1 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 503739Ban Score(100 max): 0 Likely Bad Peer: Peer IP: 173.192.30.91:7685 Time Connected: 03:50:13 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:24:48 2014 Bytes Sent: 123148968Bytes Recv: 7121759 Blocks Requested: 0 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 498915Ban Score(100 max): 0 You can then ban that IP via your firewall.. I won't be doing this personally as I will be needing to send them alerts. But there is nothing to stop you from removing a peer you deem unreliable. |
|
|
|
Tranz
Legendary
Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
June 20, 2014, 07:43:26 PM |
|
Regarding Cryptsy and other exchanges.
I do not take part in pushing any coin anywhere. I may vote for free here and there if I have a few minutes. But if it requires sending BTC to get a coin listed, it might as well just be a bribe in my opinion. I do not take part in that. If an exchange wants to list it. Here it is.
My job here is to get the wallet working, the network secure and the community excited about a coin. The rest is up to you guys.
I may work towards getting certain people or aspects on board. Such as I will soon be working on getting some high profile charities involved with HoboNickels. But that is about my fullest extent towards pushing a coin on anyone.
Let's work together to achieve the ends we all desire. Divide and concur and casting blame, isn't likely to have the desired results.
Thanks!
|
|
|
|
|
brian_23452
|
|
June 20, 2014, 09:52:33 PM |
|
SHAME ON THE DEVS OF THIS COIN FOR NOT BEING MORE AGGRESSIVE AND GETTING THIS COIN LISTED ON MORE THAN ONE EXCHANGE.
THEIR LACK OF EFFORT TO GET THIS COIN LISTED ON MORE THAN ONE EXCHANGE HAS LED TO A 40% DECLINE IN VALUE IN THE LAST 12 HOURS.
I DON'T KNOW WHO IS MORE INCOMPETENT - THEM OR CRYPTSY - THIS COIN SHOULD BE TAKEN OVER BY THE COMMUNITY - IT'S CLEAR THEY COULD CARE LESS ABOUT THEIR ABANDONED CREATION.
CTYPTSY HAS HAD THE COIN HOSTAGE FOR THE LAST WEEK - THIS SHOULD NEVER BE ALLOWED TO HAPPEN AGAIN
LET'S TRY AND GET ON POLONIEX OR MINTPAL ALSO
MY HUMBLE 2 SATOSHI
Where to even begin? 1. Dev's job is to make a good coin. Dev's job is NOT to make sure you personally can profit from mining a coin, or that it be worth a certain value. 2. Even so, the coin is at it's highest value YTD what are you complaining about? 3. The coin did not lose 40% of it's value. The coin was very temporarily and artificially inflated in price because while people could buy as much as they wanted, those holding coins couldn't get them on the exchange to sell. 4. He just came out with major changes and a new wallet (incidentally, you want him to do things but doing things is what caused this in the first place); that isn't "abandoning" the coin. Listen, if you were paying attention at all you would have known it was only listed on one exchange and that the exchange wasn't accepting deposits. Common sense could have told you that the brief run up in price was not real. If that wasn't enough, you've spent the last two weeks bragging to anyone on here that would listen about how much better at mining you were than everyone else, what a genius you are at picking coins, etc. Perhaps you will learn from this, and next time you see a well known coin with a much higher return than average, ask yourself why no one else is jumping all over it. Or you could just blame other people for your mistakes. I guess that works too. Fact is, you fucked up. You used the wrong numbers, your autoswitcher used the wrong numbers, YOU fucked up and mined the wrong thing. Not the dev. Smarten up. |
|
|
|
|
|
ymod123
|
|
June 20, 2014, 11:06:29 PM |
|
Since I updated to 2.1 yesterday the wallet is using LOTS of network bandwidth. I let it run over night and this morning it was sending at a rate of nearly 100 kb/s. Perfmon is showing Bottlecaps connections with 5-15 kb/s. Debug log is full of getblocks. Deleting peers.dat and restarting wallet doesn't fix it. What can I do?
So there are still a few people who do not know their wallet is stuck and requesting the same blocks over and over. After the fork I am going to be sending an alert to all people on 2.0 and 2.0.0.1. Advising them to check and make sure they are on the right block and that they should upgrade to 2.1 to fix a staking issue with their client. In the mean time you can click the connections bar and see if you have a bad peer. You can see a bad peer as follows. Good Peer: Peer IP: 176.37.67.61:7685 Time Connected: 18:23:58 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:27:10 2014 Bytes Sent: 795295Bytes Recv: 838737 Blocks Requested: 1 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 503739Ban Score(100 max): 0 Likely Bad Peer: Peer IP: 173.192.30.91:7685 Time Connected: 03:50:13 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:24:48 2014 Bytes Sent: 123148968Bytes Recv: 7121759 Blocks Requested: 0 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 498915Ban Score(100 max): 0 You can then ban that IP via your firewall.. I won't be doing this personally as I will be needing to send them alerts. But there is nothing to stop you from removing a peer you deem unreliable. my wallet stock stock in block 607 im using the latest fix... where can i find the connection bar? tnx |
|
|
|
|
|
FlungSpun
|
|
June 20, 2014, 11:42:44 PM |
|
I'll support the coin as long as I deem it profitable to mine.
I have no altruistic intentions.
that said - "what is good for the coin?" - to allow it to languish at 1 satoshi like so many other coins or and have people like me mine it and do everything I can do to drive up it's value...
that's my opinion...
Mining for profit is not supporting the coin, it's purely for your own enterprise. That is fine, miners are needed and very welcome but it also diminishes any opinion you have on a community thread. People who are prepared to put in real time & effort to assist other users with issues and promote adoption and services don't want to hear about you blaming everyone but yourself for your own lack of due diligence. Treat you mining enterprise like the business it should be, its dog eat dog and your choices are your own. If you want to bash the dev team for real coding and wallet issues go ahead, you'll be a while waiting for a problem that these guys don't get on top of before you have finished typing your complaint. Out of interest, can you give an example of "do everything I can do to drive up it's value"Sounds like you were trying to do everything you could to dump hard on a fake pump and never look back. |
|
|
|
|
Tranz
Legendary
Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
June 20, 2014, 11:53:09 PM |
|
Since I updated to 2.1 yesterday the wallet is using LOTS of network bandwidth. I let it run over night and this morning it was sending at a rate of nearly 100 kb/s. Perfmon is showing Bottlecaps connections with 5-15 kb/s. Debug log is full of getblocks. Deleting peers.dat and restarting wallet doesn't fix it. What can I do?
So there are still a few people who do not know their wallet is stuck and requesting the same blocks over and over. After the fork I am going to be sending an alert to all people on 2.0 and 2.0.0.1. Advising them to check and make sure they are on the right block and that they should upgrade to 2.1 to fix a staking issue with their client. In the mean time you can click the connections bar and see if you have a bad peer. You can see a bad peer as follows. Good Peer: Peer IP: 176.37.67.61:7685 Time Connected: 18:23:58 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:27:10 2014 Bytes Sent: 795295Bytes Recv: 838737 Blocks Requested: 1 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 503739Ban Score(100 max): 0 Likely Bad Peer: Peer IP: 173.192.30.91:7685 Time Connected: 03:50:13 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:24:48 2014 Bytes Sent: 123148968Bytes Recv: 7121759 Blocks Requested: 0 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 498915Ban Score(100 max): 0 You can then ban that IP via your firewall.. I won't be doing this personally as I will be needing to send them alerts. But there is nothing to stop you from removing a peer you deem unreliable. my wallet stock stock in block 607 im using the latest fix... where can i find the connection bar? tnx 607 to go, or at block 607, either way no reason for that. The connection icon is to the right of the staking arrow. I have 19 connections 3 are bad, 2 are in the process of syncing. So it looks like things are getting normal. |
|
|
|
simplemind
Member
Offline
Activity: 84
Merit: 10
|
|
June 21, 2014, 10:32:27 AM |
|
Since I updated to 2.1 yesterday the wallet is using LOTS of network bandwidth. I let it run over night and this morning it was sending at a rate of nearly 100 kb/s. Perfmon is showing Bottlecaps connections with 5-15 kb/s. Debug log is full of getblocks. Deleting peers.dat and restarting wallet doesn't fix it. What can I do?
You can then ban that IP via your firewall.. I won't be doing this personally as I will be needing to send them alerts. But there is nothing to stop you from removing a peer you deem unreliable. Banning bad peers via firewall worked, thanks. Are there plans to add some kind of peer blacklist to the wallet? Something like bannode=1.2.3.4. The Extended Peer Information window has the advantage over getpeerinfo that it shows converted date/time but it has fixed size and the text box is very small. I had to copy&paste to notepad for comfortable reading, so a variable size window would be cool. |
|
|
|
|
|
ymod123
|
|
June 21, 2014, 12:29:59 PM |
|
Since I updated to 2.1 yesterday the wallet is using LOTS of network bandwidth. I let it run over night and this morning it was sending at a rate of nearly 100 kb/s. Perfmon is showing Bottlecaps connections with 5-15 kb/s. Debug log is full of getblocks. Deleting peers.dat and restarting wallet doesn't fix it. What can I do?
So there are still a few people who do not know their wallet is stuck and requesting the same blocks over and over. After the fork I am going to be sending an alert to all people on 2.0 and 2.0.0.1. Advising them to check and make sure they are on the right block and that they should upgrade to 2.1 to fix a staking issue with their client. In the mean time you can click the connections bar and see if you have a bad peer. You can see a bad peer as follows. Good Peer: Peer IP: 176.37.67.61:7685 Time Connected: 18:23:58 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:27:10 2014 Bytes Sent: 795295Bytes Recv: 838737 Blocks Requested: 1 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 503739Ban Score(100 max): 0 Likely Bad Peer: Peer IP: 173.192.30.91:7685 Time Connected: 03:50:13 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:24:48 2014 Bytes Sent: 123148968Bytes Recv: 7121759 Blocks Requested: 0 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 498915Ban Score(100 max): 0 You can then ban that IP via your firewall.. I won't be doing this personally as I will be needing to send them alerts. But there is nothing to stop you from removing a peer you deem unreliable. my wallet stock stock in block 607 im using the latest fix... where can i find the connection bar? tnx 607 to go, or at block 607, either way no reason for that. The connection icon is to the right of the staking arrow. I have 19 connections 3 are bad, 2 are in the process of syncing. So it looks like things are getting normal. hello! I close and open the wallet again now it says out of sync but it says 8 active connection when i put my cursor to the word out of sync its says "the displaed information maybe out of date your wallet automatically synchronizes with the bottlecap network after a connection is establish but this process has not completed yet" |
|
|
|
|
Tranz
Legendary
Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
June 21, 2014, 12:35:06 PM
Last edit: June 21, 2014, 12:49:18 PM by Tranz |
|
Since I updated to 2.1 yesterday the wallet is using LOTS of network bandwidth. I let it run over night and this morning it was sending at a rate of nearly 100 kb/s. Perfmon is showing Bottlecaps connections with 5-15 kb/s. Debug log is full of getblocks. Deleting peers.dat and restarting wallet doesn't fix it. What can I do?
You can then ban that IP via your firewall.. I won't be doing this personally as I will be needing to send them alerts. But there is nothing to stop you from removing a peer you deem unreliable. Banning bad peers via firewall worked, thanks. Are there plans to add some kind of peer blacklist to the wallet? Something like bannode=1.2.3.4. The Extended Peer Information window has the advantage over getpeerinfo that it shows converted date/time but it has fixed size and the text box is very small. I had to copy&paste to notepad for comfortable reading, so a variable size window would be cool. You can hit control c on the window and paste the entire Detailed View into notepad. The popup window that I used built into QT doesn't allow size update. But one of these days when I have time I will see about popping up a more custom window, similar to the about window. It's just a lot more work. I've thought about bannode before. I may do it. I'd would hate for everyone to ban these IPs and they are not able to get connection to network, once they get themselves fixed up. |
|
|
|
Tranz
Legendary
Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
June 21, 2014, 12:37:59 PM |
|
Since I updated to 2.1 yesterday the wallet is using LOTS of network bandwidth. I let it run over night and this morning it was sending at a rate of nearly 100 kb/s. Perfmon is showing Bottlecaps connections with 5-15 kb/s. Debug log is full of getblocks. Deleting peers.dat and restarting wallet doesn't fix it. What can I do?
So there are still a few people who do not know their wallet is stuck and requesting the same blocks over and over. After the fork I am going to be sending an alert to all people on 2.0 and 2.0.0.1. Advising them to check and make sure they are on the right block and that they should upgrade to 2.1 to fix a staking issue with their client. In the mean time you can click the connections bar and see if you have a bad peer. You can see a bad peer as follows. Good Peer: Peer IP: 176.37.67.61:7685 Time Connected: 18:23:58 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:27:10 2014 Bytes Sent: 795295Bytes Recv: 838737 Blocks Requested: 1 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 503739Ban Score(100 max): 0 Likely Bad Peer: Peer IP: 173.192.30.91:7685 Time Connected: 03:50:13 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:24:48 2014 Bytes Sent: 123148968Bytes Recv: 7121759 Blocks Requested: 0 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 498915Ban Score(100 max): 0 You can then ban that IP via your firewall.. I won't be doing this personally as I will be needing to send them alerts. But there is nothing to stop you from removing a peer you deem unreliable. my wallet stock stock in block 607 im using the latest fix... where can i find the connection bar? tnx 607 to go, or at block 607, either way no reason for that. The connection icon is to the right of the staking arrow. I have 19 connections 3 are bad, 2 are in the process of syncing. So it looks like things are getting normal. hello! I close and open the wallet again now it says out of sync but it says 8 active connection when i put my cursor to the word out of sync its says "the displaed information maybe out of date your wallet automatically synchronizes with the bottlecap network after a connection is establish but this process has not completed yet" Sounds like you got stuck on the wrong chain. Please shutdown client and remove blk0001.dat and blkindex.dat and restart. Please be sure to use 2.1. Alternatively you can also try to create a DB_CONFIG file as suggested by ghostlander here: https://bitcointalk.org/index.php?topic=241445.msg7362114#msg7362114 |
|
|
|
|
ymod123
|
|
June 21, 2014, 01:17:07 PM |
|
Since I updated to 2.1 yesterday the wallet is using LOTS of network bandwidth. I let it run over night and this morning it was sending at a rate of nearly 100 kb/s. Perfmon is showing Bottlecaps connections with 5-15 kb/s. Debug log is full of getblocks. Deleting peers.dat and restarting wallet doesn't fix it. What can I do?
So there are still a few people who do not know their wallet is stuck and requesting the same blocks over and over. After the fork I am going to be sending an alert to all people on 2.0 and 2.0.0.1. Advising them to check and make sure they are on the right block and that they should upgrade to 2.1 to fix a staking issue with their client. In the mean time you can click the connections bar and see if you have a bad peer. You can see a bad peer as follows. Good Peer: Peer IP: 176.37.67.61:7685 Time Connected: 18:23:58 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:27:10 2014 Bytes Sent: 795295Bytes Recv: 838737 Blocks Requested: 1 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 503739Ban Score(100 max): 0 Likely Bad Peer: Peer IP: 173.192.30.91:7685 Time Connected: 03:50:13 Time of Last Send: Fri Jun 20 15:27:10 2014 Time of Last Recv: Fri Jun 20 15:24:48 2014 Bytes Sent: 123148968Bytes Recv: 7121759 Blocks Requested: 0 Version: 70003 SubVersion: /Satoshi:0.7.5/ Inbound?: Y Starting Block: 498915Ban Score(100 max): 0 You can then ban that IP via your firewall.. I won't be doing this personally as I will be needing to send them alerts. But there is nothing to stop you from removing a peer you deem unreliable. my wallet stock stock in block 607 im using the latest fix... where can i find the connection bar? tnx 607 to go, or at block 607, either way no reason for that. The connection icon is to the right of the staking arrow. I have 19 connections 3 are bad, 2 are in the process of syncing. So it looks like things are getting normal. hello! I close and open the wallet again now it says out of sync but it says 8 active connection when i put my cursor to the word out of sync its says "the displaed information maybe out of date your wallet automatically synchronizes with the bottlecap network after a connection is establish but this process has not completed yet" Sounds like you got stuck on the wrong chain. Please shutdown client and remove blk0001.dat and blkindex.dat and restart. Please be sure to use 2.1. Alternatively you can also try to create a DB_CONFIG file as suggested by ghostlander here: https://bitcointalk.org/index.php?topic=241445.msg7362114#msg7362114thanks Ill try that |
|
|
|
|
ryanb
Legendary
Offline
Activity: 1148
Merit: 1000
|
|
June 21, 2014, 02:14:01 PM |
|
my CAPS address is not showing on http://cap.blockx.info/richlist/is it safe for me to buy more CAP from cryptsy and have them transferred to my address? |
|
|
|
Tranz
Legendary
Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
June 21, 2014, 02:35:39 PM |
|
Yes if you are on the correct block, currently 505952+ you are good to go. Unick has said that is not fully functional yet. |
|
|
|
ryanb
Legendary
Offline
Activity: 1148
Merit: 1000
|
|
June 21, 2014, 02:37:47 PM |
|
Yes if you are on the correct block, currently 505952+ you are good to go. Unick has said that is not fully functional yet. i am redownloading the blockchain just to be on the safe side. Thanks |
|
|
|
presstab
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
June 21, 2014, 05:31:45 PM |
|
Yes if you are on the correct block, currently 505952+ you are good to go. Unick has said that is not fully functional yet. i am redownloading the blockchain just to be on the safe side. Thanks You can always try a small transfer first and if it goes through then send the rest. I often do this when transferring large amounts to and from cryptsy. |
|
|
|
|
unick
|
|
June 21, 2014, 06:55:56 PM |
|
yes it's safe, if the address is not showing up on the list, likely it's because the script has been stuck somewhere, it doesn't not mean something is wrong with your address. I need to put some more work into the explorer before it is fully functional. Soon I will have more time (hopefully  ) |
|
|
|
|
unick
|
|
June 21, 2014, 07:00:48 PM |
|
SHAME ON THE DEVS OF THIS COIN FOR NOT BEING MORE AGGRESSIVE AND GETTING THIS COIN LISTED ON MORE THAN ONE EXCHANGE.
THEIR LACK OF EFFORT TO GET THIS COIN LISTED ON MORE THAN ONE EXCHANGE HAS LED TO A 40% DECLINE IN VALUE IN THE LAST 12 HOURS.
I DON'T KNOW WHO IS MORE INCOMPETENT - THEM OR CRYPTSY - THIS COIN SHOULD BE TAKEN OVER BY THE COMMUNITY - IT'S CLEAR THEY COULD CARE LESS ABOUT THEIR ABANDONED CREATION.
CTYPTSY HAS HAD THE COIN HOSTAGE FOR THE LAST WEEK - THIS SHOULD NEVER BE ALLOWED TO HAPPEN AGAIN
LET'S TRY AND GET ON POLONIEX OR MINTPAL ALSO
MY HUMBLE 2 SATOSHI
this attitude is not going to get you anywhere. you're concern about having more exchanges is justified, but your rant against the devs is not. It's a community effort after all if a coin gets somewhere. instead of shamefully blaming dev about this issue, you should use your energy and words to get people work together in achieving a desired goal. did you contact poloniex? did you contact allcoin? did you contact bittrex? did you contact atomic-trade ? do so before complaining about this. and then when it's done... just DON'T COMPLAIN! |
|
|
|
|
cryptmebro
|
|
June 21, 2014, 07:39:10 PM |
|
Can we get a link to 2.1? Nothing on the OP, BC foundation github, or trans5 github. Really should be in the OP
|
|
|
|
|
|
Poll
