Pages:
Author

Topic: [ANN] 42-coin Development Discussion Thread - page 25. (Read 105292 times)

hero member
Activity: 1946
Merit: 867
Defend Bitcoin and its PoW: bitcoincleanup.com
https://novaexchange.com/market/BTC_42/

  You can now trade at ~NOVA EXCHANGE~

If I remember correctly Novaexchange has been around for a while correct? I must say I have never used them. What's the experience with them?
member
Activity: 183
Merit: 12
https://novaexchange.com/market/BTC_42/

  You can now trade at ~NOVA EXCHANGE~
hero member
Activity: 1946
Merit: 867
Defend Bitcoin and its PoW: bitcoincleanup.com
And some news from Cryptopia:

"If you held balances in coins that were lost in the event you will start to see Withdraws on your account for those coins. The TXID for the withdraw will not exist on the network but will detail how the coin was impacted in the event. For each withdraw you will also see a subsequent deposit of Cryptopia Loss Marker(CLM), the TXID for this will also not exist on a network but will detail the coin it represents a loss for. CLM is not a coin, it can't be traded as yet, it is just a number in the database that represents the loss for each coin for each user in $NZD at the time of the event. There are still steps to take to ensure we are taking a legal path toward reimbursement."



At least they are trying, but I think it will take them a while to regain the traction they now lost because of this breach of trust.

Oh yes, I think it will!!

Don't know. It's not easy to forget about that. If you were a customer there and lost funds once, would you want to risk it again?

Oh, that's what I meant, tiCeR. It will be an uphill battle for Topia to regain trust (certainly if they continue to communicate as poorly as they have thus far!!).

Other exchanges have recovered from hacks in the past, but I think it will be tougher to do now than it has been some years ago. Too many other options out there.

Great point. I recently had a little scratch around a re-opened CEX: same clumsy design as previously; middling communication from those in charge; and maxi-Verification (because they're in the EU). Not very encouraging.

If you don't have to use a new one, stick with those you have positive experience with. I gave some CEXs a try here and there with little money, and some of them just disappeared. Not talking big amounts here, but still it's not worth a try unless there is sufficient evidence that it's legit.
jr. member
Activity: 226
Merit: 2
42-coin ROI    -98.91%

ROI= The approximate return on investment if purchased at the time of launch (or earliest known price)
  info from: https://coinmarketcap.com/currencies/42-coin/#charts
 
This is funny!It's time to buy!!!

Wow.

All Time Low   $8.99 USD (May 12, 2016)
member
Activity: 183
Merit: 12
42-coin ROI    -98.91%

ROI= The approximate return on investment if purchased at the time of launch (or earliest known price)
  info from: https://coinmarketcap.com/currencies/42-coin/#charts
 
This is funny!It's time to buy!!!
member
Activity: 790
Merit: 26
And some news from Cryptopia:

"If you held balances in coins that were lost in the event you will start to see Withdraws on your account for those coins. The TXID for the withdraw will not exist on the network but will detail how the coin was impacted in the event. For each withdraw you will also see a subsequent deposit of Cryptopia Loss Marker(CLM), the TXID for this will also not exist on a network but will detail the coin it represents a loss for. CLM is not a coin, it can't be traded as yet, it is just a number in the database that represents the loss for each coin for each user in $NZD at the time of the event. There are still steps to take to ensure we are taking a legal path toward reimbursement."



At least they are trying, but I think it will take them a while to regain the traction they now lost because of this breach of trust.

Oh yes, I think it will!!

Don't know. It's not easy to forget about that. If you were a customer there and lost funds once, would you want to risk it again?

Oh, that's what I meant, tiCeR. It will be an uphill battle for Topia to regain trust (certainly if they continue to communicate as poorly as they have thus far!!).

Other exchanges have recovered from hacks in the past, but I think it will be tougher to do now than it has been some years ago. Too many other options out there.

Great point. I recently had a little scratch around a re-opened CEX: same clumsy design as previously; middling communication from those in charge; and maxi-Verification (because they're in the EU). Not very encouraging.
hero member
Activity: 1946
Merit: 867
Defend Bitcoin and its PoW: bitcoincleanup.com
And some news from Cryptopia:

"If you held balances in coins that were lost in the event you will start to see Withdraws on your account for those coins. The TXID for the withdraw will not exist on the network but will detail how the coin was impacted in the event. For each withdraw you will also see a subsequent deposit of Cryptopia Loss Marker(CLM), the TXID for this will also not exist on a network but will detail the coin it represents a loss for. CLM is not a coin, it can't be traded as yet, it is just a number in the database that represents the loss for each coin for each user in $NZD at the time of the event. There are still steps to take to ensure we are taking a legal path toward reimbursement."



At least they are trying, but I think it will take them a while to regain the traction they now lost because of this breach of trust.

Oh yes, I think it will!!

Don't know. It's not easy to forget about that. If you were a customer there and lost funds once, would you want to risk it again?

Oh, that's what I meant, tiCeR. It will be an uphill battle for Topia to regain trust (certainly if they continue to communicate as poorly as they have thus far!!).

Other exchanges have recovered from hacks in the past, but I think it will be tougher to do now than it has been some years ago. Too many other options out there.
member
Activity: 790
Merit: 26
On the Telegram thread, mike is calling for some marketing initiatives, which I think is a great idea. So we are going to discuss that.



why do not you discuss it in the telegram chat. I think, that's exactly, what it was created for. many people can share their thoughts and decisions. it is my desire to communicate with other participants and learn more new and interesting

Okay! I was just afk for a couple of days. We can discuss anything anwhere
sr. member
Activity: 840
Merit: 251
On the Telegram thread, mike is calling for some marketing initiatives, which I think is a great idea. So we are going to discuss that.



why do not you discuss it in the telegram chat. I think, that's exactly, what it was created for. many people can share their thoughts and decisions. it is my desire to communicate with other participants and learn more new and interesting
member
Activity: 790
Merit: 26
On the Telegram thread, mike is calling for some marketing initiatives, which I think is a great idea. So we are going to discuss that.

legendary
Activity: 1155
Merit: 1174
https://t.me/laser9un
seems needlessly obtuse to have two layers of different versioning.

oh well, getinfo should report the subversion or better still getnetworkinfo should be implemented.

Good point. Thank you. Version reporting will be more clear in the next release.
dnp
full member
Activity: 401
Merit: 110
what (and where) is the correct current wallet?
i've been running 42-v0.0.9-bdb-mingw for a while, but notice all my peer connections
are version 0.7.6.9 or 0.7.7.1
and i have no peers at all for 0.0.9

0.7.6.9 and 0.7.7.1 are sub-versions, both are actual:

42-v0.0.9 have sub-version Satoshi:0.7.7.1 (Win, MacOS, Linux) and Satoshi:0.7.7.2 (Android),
42-v0.0.8 have sub-version Satoshi:0.7.6.9 (Win, MacOS, Linux) and Satoshi:0.7.7.0 (Android).

seems needlessly obtuse to have two layers of different versioning.

oh well, getinfo should report the subversion or better still getnetworkinfo should be implemented.
legendary
Activity: 1155
Merit: 1174
https://t.me/laser9un
what (and where) is the correct current wallet?
i've been running 42-v0.0.9-bdb-mingw for a while, but notice all my peer connections
are version 0.7.6.9 or 0.7.7.1
and i have no peers at all for 0.0.9

0.7.6.9 and 0.7.7.1 are sub-versions, both are actual:

42-v0.0.9 have sub-version Satoshi:0.7.7.1 (Win, MacOS, Linux) and Satoshi:0.7.7.2 (Android),
42-v0.0.8 have sub-version Satoshi:0.7.6.9 (Win, MacOS, Linux) and Satoshi:0.7.7.0 (Android).
dnp
full member
Activity: 401
Merit: 110
what (and where) is the correct current wallet?
i've been running 42-v0.0.9-bdb-mingw for a while, but notice all my peer connections
are version 0.7.6.9 or 0.7.7.1
and i have no peers at all for 0.0.9

member
Activity: 790
Merit: 26
And some news from Cryptopia:

"If you held balances in coins that were lost in the event you will start to see Withdraws on your account for those coins. The TXID for the withdraw will not exist on the network but will detail how the coin was impacted in the event. For each withdraw you will also see a subsequent deposit of Cryptopia Loss Marker(CLM), the TXID for this will also not exist on a network but will detail the coin it represents a loss for. CLM is not a coin, it can't be traded as yet, it is just a number in the database that represents the loss for each coin for each user in $NZD at the time of the event. There are still steps to take to ensure we are taking a legal path toward reimbursement."



At least they are trying, but I think it will take them a while to regain the traction they now lost because of this breach of trust.

Oh yes, I think it will!!

Don't know. It's not easy to forget about that. If you were a customer there and lost funds once, would you want to risk it again?

Oh, that's what I meant, tiCeR. It will be an uphill battle for Topia to regain trust (certainly if they continue to communicate as poorly as they have thus far!!).
hero member
Activity: 1946
Merit: 867
Defend Bitcoin and its PoW: bitcoincleanup.com
And some news from Cryptopia:

"If you held balances in coins that were lost in the event you will start to see Withdraws on your account for those coins. The TXID for the withdraw will not exist on the network but will detail how the coin was impacted in the event. For each withdraw you will also see a subsequent deposit of Cryptopia Loss Marker(CLM), the TXID for this will also not exist on a network but will detail the coin it represents a loss for. CLM is not a coin, it can't be traded as yet, it is just a number in the database that represents the loss for each coin for each user in $NZD at the time of the event. There are still steps to take to ensure we are taking a legal path toward reimbursement."



At least they are trying, but I think it will take them a while to regain the traction they now lost because of this breach of trust.

Oh yes, I think it will!!

Don't know. It's not easy to forget about that. If you were a customer there and lost funds once, would you want to risk it again?
member
Activity: 790
Merit: 26
42 wallet online again at LIVECOIN!

Up again here (dawn Western Australia Saturday 23/3), Than; but let's keep an eye on it.
member
Activity: 183
Merit: 12
42 wallet online again at LIVECOIN!
legendary
Activity: 1155
Merit: 1174
https://t.me/laser9un
I have about .35 lost from cryptopia as well.  The following below is completely missing from the blockchain and cryptopia would not supply the private key to the wallet.

Here is a overview of your transactions including TXid’s
...

Where have you been for more than two years?
All these transactions have reached their destination.
newbie
Activity: 10
Merit: 0
I have about .35 lost from cryptopia as well.  The following below is completely missing from the blockchain and cryptopia would not supply the private key to the wallet.

Here is a overview of your transactions including TXid’s

281141

404

Debit_AP

4THvZQXjLfhkF3zWNtzi1cbSdKzeo1b8Sh

0.040010210000000000000000000000

2017-01-24 06:24:40

c118f3e4e1d11696ae8168f5a44610555843c361a9649ee723ad0bdb545d7d87

274914

404

Debit_MP

4THvZQXjLfhkF3zWNtzi1cbSdKzeo1b8Sh

0.011593800000000000000000000000

2017-01-23 07:39:38

9842725d320550f78a4a7e7443ce622bb9f73e9fd5d5282bc134aefefd2ead14

271017

404

Debit_MP

4THvZQXjLfhkF3zWNtzi1cbSdKzeo1b8Sh

0.010514440000000000000000000000

2017-01-23 01:15:34

0e9ebfa7a810b962c96c0c6b4aa11d01ff606abe2cf9c1cf7fddae806fb91277

267710

404

Debit_MP

4THvZQXjLfhkF3zWNtzi1cbSdKzeo1b8Sh

0.012370980000000000000000000000

2017-01-22 18:24:36

8562010b5a88f971cd2c0d76e07a90d5840fcdbdc3e5c6ad362868c04dceaf2e

265055

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.009253530000000000000000000000

2017-01-22 12:27:33

74a96660dbc60937d346ce1e02ccd5f90cd3170715645fba7300629588c64461

262182

404

Debit_MP

4THvZQXjLfhkF3zWNtzi1cbSdKzeo1b8Sh

0.026499860000000000000000000000

2017-01-22 05:51:34

5563013d0c26ea3d76b601c4fe329903ca247f123fdb01cbe368795034562a87

248420

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.020000000000000000000000000000

2017-01-20 11:21:36

953cd425f5c7f9e43ae3cf41a48327f2c97250151ea40a86c73c443a6501df99

248419

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.015000000000000000000000000000

2017-01-20 11:21:36

ef947d9553c37b2543c6c35feb474cac81a9dd5225e472afecaf502c9759bc55

248418

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.015000000000000000000000000000

2017-01-20 11:21:36

b95ecbbcdc38eaebc37686a1d3f2f36f747fd6b297866b8d43495be3e32bb5fc

248401

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.015000000000000000000000000000

2017-01-20 11:21:36

848abd21d932a5e4f1dfeb86ba9b68da9e7cd88b11927d13d51df3f2fa05231d

248400

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.015000000000000000000000000000

2017-01-20 11:21:36

dc36305551d87d523abe8ae4af82ee04e16760f4cf55c4c91ddd1dfe3b2f0177

248399

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.020000000000000000000000000000

2017-01-20 11:21:36

515360f624a2896305c96018f0b769c78d2f70332548bb3ddc9f29e1db4b5b5b

248398

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.030000000000000000000000000000

2017-01-20 11:21:36

b98794cc20abdc9d6b4b229ec94d3e99e1c29e5c1717ba39b26d63aa8cee2d10

248048

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.015000000000000000000000000000

2017-01-20 11:21:36

9e783e2d0638b5cd379904228fcea7a396e94e0b43d52e894df7848d0f24812d

248047

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.015000000000000000000000000000

2017-01-20 11:21:36

158e8d89bbbec1ccd370e9b19df15b522dc00765189fb15b5e9ba3d54c0e48b1

248046

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.015000000000000000000000000000

2017-01-20 11:21:36

9afe6790de67ee31b362a2b26a6fbe7e6b68b15691dabaabad4cdd9221517b56

248045

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.020000000000000000000000000000

2017-01-20 11:21:36

27d1ab8ce3ec2de2ed6d7acd3d1b72d0c1ef1fbf6f6984da4c264e45d22daea1

248044

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.020000000000000000000000000000

2017-01-20 11:21:36

74fa21662ea42ebe8531053a5191b0a72a2217be02c4f2fbf570b00c1452cdd9

248043

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.020000000000000000000000000000

2017-01-20 11:21:36

1e3495458617bf3522c275a29c76209b2c02797f1c0cc5d99feb90006c6f239c

248042

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.030000000000000000000000000000

2017-01-20 11:21:36

e7e0dd344c1cc9238dcc5a949230aefba7c47c192d49e41bd5aacfbee1a58422

248041

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.030000000000000000000000000000

2017-01-20 11:21:36

673b9b57ac8a596ae857c90ab880f7d2ffd491369face45a195914f9a19f98b3

248040

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.010000000000000000000000000000

2017-01-20 11:21:36

08c28360228b6529b389ad23bc2e88c88420f4c02070a450acd31af6479eaf31

248039

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.030000000000000000000000000000

2017-01-20 11:21:36

fdd2d4ac43f7988a196785c98cbec43154907630d40ed9ec0586df9378addc95

207329

404

Debit_MP

4FL3PBNqkELyMnuozP7FH42uF18CXrqunu

0.046753220000000000000000000000

2017-01-20 11:21:36

f6f720fccab2ee3f8d50da4ec4eab3382e133d0bce43f0f5e214ccc390dee8c4
Pages:
Jump to: