Scam..

This token is starting to look like a scam to just bleed BTC and ETH from users. They airdropped this token and have given the same response over a period of 4 months now saying the technical details blah blah blah. I'd be very wary sending these guys any Eth or BTC in their Back-orifice to get CNX tokens. If you already have the exchange between Eth and BTC working in your back office why cant we send our CNX ERC-20 tokens to that same office to exchange? It's a bit silly that you've continued to give the same response copy and pasted for over 4 months.

They are just trying to pump their token, get on exchanges, and bleed the BTC and Eth away from users who don't know any better. If their product / tech is so good, why is it completely lacking in vision and delivery? The only updates they give on twitter are how the price is rising. Nothing about their technological challenges or hurdles.

This site / ICO is a complete scam. Their site is down and not even online any longer. Anything bidlend related - stay away from, its a scam.

Hundreds of people have petitioned them and we still have no answers. They are ignoring this token and community for some reason. I personally sent it to Bittrex before they changed their process to where you have to be the token creator to submit it and all this shit. Can't wait until the platform is online.

I am in the same boat Rigby, I feel your pain. It's looking pretty bleak. Newegg has become pretty strict, their system is almost on lockdown with ordering more than one video card right now.

Total troll. If you understood the technology you wouldn't even be posting this. Guess what ' Mr. Economist" depending on need and function over time there may even be thousands or hundreds of thousands of "coins"

Slim Shady over there... 
He's got Pandaminers and everyting...

I did as well! Bittrex would be a great exchange for VERI    I am in open agreement on that #slack channel, Team Veritaseum!

Thank you for the info. That's what I get for being a cheapskate....  

I now realize after I did my first zapwallet it cleared that transaction! So it is no longer broadcasting on my end. Is my thinking correct on this?

I believe I found the culprit!! I had a transaction that became stuck and it's still confirming with that same wallet address. Assuming this would be the cause, yes? Because this was removed on my end I will have to wait for it to broadcast back to me that , that particular transaction went through?

https://blockchain.info/tx/d0c08a72bc3d22f9d587a68f86e5d1c1473ee75332c892cb27499b5f68abe6f5

It all started last night where I sent a tx just fine and then attempted to do another and then the transaction sat at unconfirmed w/ 6 nodes eventually it moved to the dreaded 0/unconfirmed, in memory pool. The TX fee was high as well. So I ended up getting impatient and after doing a little research I ran the really fun process of -zapwallet  . I was happy, the tx cleared and I felt I was good to go. Today I decided to attempt to send to that same address and then it happens again, even though I used the recommended tx fee to max. So that new transaction did the same thing to me, and again I ran a -zapwallet, but this time the tx didn't clear and its just sitting at Status: 0/unconfirmed, in memory pool. I have also tried renaming mempool.dat to attempt to clear cache and that will not work either. Should I just wait 72 hours and why could I potentially be seeing so many failures? Turned off Firewall just in case it didn't like update to 0.14

Will running -mempoolexpiry= or -maxo potentially speed the process up of this transaction returning back to me or confirming? And what could be causing all these failures even though I am putting these tx to max fee

 I am using Bitcoin Core and these are the tx's that will not clear no matter what I do.

Tx#1

Date: 5/27/2017 17:02
To:
Debit: -0.50000000 BTC
Transaction fee: -0.00180637 BTC
Net amount: -0.50180637 BTC
Transaction ID: 15dca08c2a71c72adf24b0a36c13f0bae54f6964e940d50ab30143ef7515d396
Transaction total size: 521 bytes
Output index: 1

Tx#2

Status: 0/unconfirmed, in memory pool
Date: 5/27/2017 16:07
To:
Debit: -0.50000000 BTC
Transaction fee: -0.00216402 BTC 00            ----
Net amount: -0.50216402 BTC
Transaction ID: 65347cb71a795b61ef50e296957ad64c6325fb4caa681403c9f4baa17a0a9551
Transaction total size: 373 bytes
Output index: 1

PS. Could I potentially be connecting to a bad node that is somehow causing this backup for me???

The future tx fee's will be a more ridiculous number. That I can assure ypu