[ANN] [CPU mining] Yenten v2.0.1 [YTN] [YescryptR16] [Exchange avilable]

[netto7]

today price drop to 36sat

[slovakia]

shitcoin 

[Vova1234]

When new blocks arrive in the wallet, it starts to hang.

What could be the problem?

MPOS began to hang after a long time delay API RPC query for wallet.

[AlecMe]

wallet 2,0,1 will not work for me on mac os and i am on old wallet. does it influence me receiving my coins from mining on my wallet address ?

[Guzek71]

######## WARNING #########

The Yenten discord is start to censor every users that may ask questions, as:
- Why Conan developer has abandoned Yenten
- Who is in charge of the development now
- Why no one care about the Yenten bug, and the risk of delisting from exchanges (they got already multiples issues with wallet update)
- No updates, nothing since june, just ask for updates on Yenten discord channel and you get instantly ban

I ask on discord about my problem because of the bug (on mac), i still have around 75000 Yenten on my mac wallet, and i can’t access on it !!
I ask for help on discord, and the result was: i got ban !!!

Something is going on with Yenten, and discord admins try to hide and censore anyone asking about it.

Someone suggest that i contact YescriptR16 developers from another coins...
Please beware of Yenten since no developer on ship, and censorship.
When (and if) i can fix my wallet problem, i will dump Yenten asap ! I can’t bear it anymore the lack of professionalism !!

######## WARNING #########

I can confirm this.
They kick me out of discord only for questions.
I sold my holding after that.

If censorship, then why do the long posts from newbies remain here? You idiots who couldn't hang on to the coin need to move on! Nobody is going to hand you free money!Well besides who ever is willing to pay you to register your
 new accounts here and post this crap.

I think is time for you to wake up (no offense).
Yenten is done, wallet have instabilities, developer is gone for good, price crash and going to zero!
Who can still believe in this shitcoin ?!
Yenten is doing to zero, so accept your lost and move on !
Becaus when delisting will happens thoses who didn’t sell will be rekt for good!

[Guzek71]

wallet 2,0,1 will not work for me on mac os and i am on old wallet. does it influence me receiving my coins from mining on my wallet address ?

Developer is gone, and there is nobody to fix or take over the Yenten.
Better to get ride of your coin and mine others cpu coins.
Not a financial advice, i’m just a ex-Yenten holder and i sold it all.

[ohashi3d]

I've just tried synchronizing with v1.3.1 daemon and the backup block data at May 25th.

...
2018-10-20 01:31:54 UpdateTip: new best=00000007876142530eaeca32e71d38179480cbebc45fe964fbe0c3e84b012493  height=248957  log2_work=45.519688  tx=1106206  date=2018-10-15 17:10:23 progress=0.997061
2018-10-20 01:31:54 ProcessBlock: ACCEPTED
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 267, prev=00000025418b7351588bbcbb9c957a6c3a581bd10b433952aef3d694edc68763
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 268, prev=000000374b9231b2bae0534cd3d4e35924f32a81184aac6eef209697330e2123
2018-10-20 01:31:54 ERROR: CheckTransaction() : duplicate inputs
2018-10-20 01:31:54 ERROR: CheckBlock() : CheckTransaction failed
2018-10-20 01:31:54 ERROR: ProcessBlock() : CheckBlock FAILED
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 269, prev=0000002593846bb0d8716c00fbf30132c497b42e70315a0f65404ed129fc2e4a
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 270, prev=0000002390e6be74008db3fd88a144657de442cf03f72e9f8a2e446fd6f304f1
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 271, prev=000000356605da7b259ec6893892b320bfd305d68edddc92e71fb64da1ba6f50
...


After block 248957, "duplicate inputs" message emerged, so sure enough, there was attacks, I think.

Interestingly, v1.3.1 daemon didn't stop synchronizing after block 248958.
It processed 300+ orphan blocks, and recorded hash values below:
  height=248958: 00000022193d53b1aa17ac7b86fce2ceecbaba36f0e6d2a0a483c227d7aa4d67
  height=248959: 00000013b54daf77086e740d4e0d7721afd933614c84321c54d2f4d85e553d42
These are same as the values on the Yenten Explorer https://ytn.overemo.com/

So...now, the Yenten blockchain became quite unhealthy...we will get different hash value from different version nodes.
CVE-2018-17144-fixed wallet may be useless in this situation...


And "duplicate inputs" messages still continue emerging on debug.log...it looks hopeless for me, unfortunately.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - - - - - - - - -
Edited:

I've deleted my CVE-2018-17144-fixed Windows binaries:
https://github.com/ohashi3d/yenten/releases/tag/2.0.1fix_CVE-2018-17144

Though I may still try running Yenten daemon for my technical interest,
Good bye Yenten, for a while, or eternally...

[Vova1234]

I've just tried synchronizing with v1.3.1 daemon and the backup block data at May 25th.

...
2018-10-20 01:31:54 UpdateTip: new best=00000007876142530eaeca32e71d38179480cbebc45fe964fbe0c3e84b012493  height=248957  log2_work=45.519688  tx=1106206  date=2018-10-15 17:10:23 progress=0.997061
2018-10-20 01:31:54 ProcessBlock: ACCEPTED
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 267, prev=00000025418b7351588bbcbb9c957a6c3a581bd10b433952aef3d694edc68763
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 268, prev=000000374b9231b2bae0534cd3d4e35924f32a81184aac6eef209697330e2123
2018-10-20 01:31:54 ERROR: CheckTransaction() : duplicate inputs
2018-10-20 01:31:54 ERROR: CheckBlock() : CheckTransaction failed
2018-10-20 01:31:54 ERROR: ProcessBlock() : CheckBlock FAILED
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 269, prev=0000002593846bb0d8716c00fbf30132c497b42e70315a0f65404ed129fc2e4a
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 270, prev=0000002390e6be74008db3fd88a144657de442cf03f72e9f8a2e446fd6f304f1
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 271, prev=000000356605da7b259ec6893892b320bfd305d68edddc92e71fb64da1ba6f50
...


After block 248957, "duplicate inputs" message emerged, so sure enough, there was attacks, I think.

Interestingly, v1.3.1 daemon didn't stop synchronizing after block 248958.
It processed 300+ orphan blocks, and recorded hash values below:
  height=248958: 00000022193d53b1aa17ac7b86fce2ceecbaba36f0e6d2a0a483c227d7aa4d67
  height=248959: 00000013b54daf77086e740d4e0d7721afd933614c84321c54d2f4d85e553d42
These are same as the values on the Yenten Explorer https://ytn.overemo.com/

So...now, the Yenten blockchain became quite unhealthy...we will get different hash value from different version nodes.
CVE-2018-17144-fixed wallet may be useless in this situation...


And "duplicate inputs" messages still continue emerging on debug.log...it looks hopeless for me, unfortunately.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - - - - - - - - -
Edited:

I've deleted my CVE-2018-17144-fixed Windows binaries:
https://github.com/ohashi3d/yenten/releases/tag/2.0.1fix_CVE-2018-17144

Though I may still try running Yenten daemon for my technical interest,
Good bye Yenten, for a while, or eternally...

I have also downloaded the blockchain since May 20 and nothing has stuck with me.

https://i.13.yt/2018/10/20/1540012589-9293.png

But the problem is that when receiving new blocks, the wallet checks the blockchain and API RPC begins to respond to the request for a long time.

Code:

2018-10-20 05:04:18 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 00000022193d53b1aa17ac7b86fce2ceecbaba36f0e6d2a0a483c227d7aa4d67, bad-version(0x00000002), rejected nVersion=0x00000002 block (code 17)
2018-10-20 05:04:18 ERROR: invalid header received

[ptdvz]

I've just tried synchronizing with v1.3.1 daemon and the backup block data at May 25th.

...
2018-10-20 01:31:54 UpdateTip: new best=00000007876142530eaeca32e71d38179480cbebc45fe964fbe0c3e84b012493  height=248957  log2_work=45.519688  tx=1106206  date=2018-10-15 17:10:23 progress=0.997061
2018-10-20 01:31:54 ProcessBlock: ACCEPTED
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 267, prev=00000025418b7351588bbcbb9c957a6c3a581bd10b433952aef3d694edc68763
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 268, prev=000000374b9231b2bae0534cd3d4e35924f32a81184aac6eef209697330e2123
2018-10-20 01:31:54 ERROR: CheckTransaction() : duplicate inputs
2018-10-20 01:31:54 ERROR: CheckBlock() : CheckTransaction failed
2018-10-20 01:31:54 ERROR: ProcessBlock() : CheckBlock FAILED
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 269, prev=0000002593846bb0d8716c00fbf30132c497b42e70315a0f65404ed129fc2e4a
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 270, prev=0000002390e6be74008db3fd88a144657de442cf03f72e9f8a2e446fd6f304f1
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 271, prev=000000356605da7b259ec6893892b320bfd305d68edddc92e71fb64da1ba6f50
...


After block 248957, "duplicate inputs" message emerged, so sure enough, there was attacks, I think.

Interestingly, v1.3.1 daemon didn't stop synchronizing after block 248958.
It processed 300+ orphan blocks, and recorded hash values below:
  height=248958: 00000022193d53b1aa17ac7b86fce2ceecbaba36f0e6d2a0a483c227d7aa4d67
  height=248959: 00000013b54daf77086e740d4e0d7721afd933614c84321c54d2f4d85e553d42
These are same as the values on the Yenten Explorer https://ytn.overemo.com/

So...now, the Yenten blockchain became quite unhealthy...we will get different hash value from different version nodes.
CVE-2018-17144-fixed wallet may be useless in this situation...


And "duplicate inputs" messages still continue emerging on debug.log...it looks hopeless for me, unfortunately.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - - - - - - - - -
Edited:

I've deleted my CVE-2018-17144-fixed Windows binaries:
https://github.com/ohashi3d/yenten/releases/tag/2.0.1fix_CVE-2018-17144

Though I may still try running Yenten daemon for my technical interest,
Good bye Yenten, for a while, or eternally...

I have also downloaded the blockchain since May 20 and nothing has stuck with me.

https://i.13.yt/2018/10/20/1540012589-9293.png

But the problem is that when receiving new blocks, the wallet checks the blockchain and API RPC begins to respond to the request for a long time.

Code:

2018-10-20 05:04:18 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 00000022193d53b1aa17ac7b86fce2ceecbaba36f0e6d2a0a483c227d7aa4d67, bad-version(0x00000002), rejected nVersion=0x00000002 block (code 17)
2018-10-20 05:04:18 ERROR: invalid header received

Interesting. I've just taken a look at a 1.3.1 node that has been running for about 6 months in a pretty much forgotten about state. It claims to be at block 250640 (which is ahead of https://ytn.overemo.com/ ??).

 

Code:

UpdateTip: new best=000029414a8b9de4db77a05642d151b599ddca8699e880e4a49e19ca195f0060  height=250640  log2_work=45.519709  tx=1108289  date=2018-10-20 08:09:06 progress=1.000000
ProcessBlock: ACCEPTED

Seems to the running OK as far as i can tell. Just tons of entries like this popping up:

Code:

ProcessBlock: ORPHAN BLOCK 751, prev=00000014df02f9c0a9040ca6877927ae046057f78eb3a8909ecb41d5c4753c6e
ERROR: CheckTransaction() : duplicate inputs
ERROR: CheckBlock() : CheckTransaction failed

Code:

ERROR: AcceptToMemoryPool : nonstandard transaction: non-final

Edit: I haven't really followed this so is 1.3.1 not affected by this bug and what is the advantage of running 2.0.1 anyways?

[luk1999]

I think is time for you to wake up (no offense).
Yenten is done, wallet have instabilities, developer is gone for good, price crash and going to zero!
Who can still believe in this shitcoin ?!
Yenten is doing to zero, so accept your lost and move on !
Becaus when delisting will happens thoses who didn’t sell will be rekt for good!

Developer is gone, and there is nobody to fix or take over the Yenten.
Better to get ride of your coin and mine others cpu coins.
Not a financial advice, i’m just a ex-Yenten holder and i sold it all.

So you've sold your Yentens and registered here only to say this to us, because you're worring about someone coins.  Such a good samaritan...

IMO you're just trying to use a current situation to make a panic, so people will start selling their Yentens for any price... And when the price will drop to some (acceptable to you) level, you'll buy them.

I was checking from time to time transaction on STEX since 16th. There were some "big transactions" (60k, one for >100k...) which significally lowered coin price. It is pretty suspicious, because price on other exchanges haven't changed too much.

[ptdvz]

I think is time for you to wake up (no offense).
Yenten is done, wallet have instabilities, developer is gone for good, price crash and going to zero!
Who can still believe in this shitcoin ?!
Yenten is doing to zero, so accept your lost and move on !
Becaus when delisting will happens thoses who didn’t sell will be rekt for good!

Developer is gone, and there is nobody to fix or take over the Yenten.
Better to get ride of your coin and mine others cpu coins.
Not a financial advice, i’m just a ex-Yenten holder and i sold it all.

So you've sold your Yentens and registered here only to say this to us, because you're worring about someone coins.  Such a good samaritan...

IMO you're just trying to use a current situation to make a panic, so people will start selling their Yentens for any price... And when the price will drop to some (acceptable to you) level, you'll buy them.

I was checking from time to time transaction on STEX since 16th. There were some "big transactions" (60k, one for >100k...) which significally lowered coin price. It is pretty suspicious, because price on other exchanges haven't changed too much.

Agreed. While the current situation doesn't look good his posts seem a bit overly emotional. I mean, seriously, at current prices how many of those coins do you have to hold for it to make any kind of serious impact if they go to zero? "rekt for good"... Yeah, maybe if you hold millions. Otherwise who cares lol?

[ptdvz]

Poking around my node it seems out of 8 peers i have a single one on 2.0.1 and it's also the only one with a banscore above zero (it's at 10 actually). To me it looks like 1.3.1 is OK while 2.0.1 is causing problems?

[0xcitchx]

https://pool.cnode.id/

No registration is required
Automatic payouts every 2 hours for all balances above 0.001
Fee 0.5%

Code:

-a yescryptR16 -o stratum+tcp://pool.cnode.id:6301 -u WALLET_ADDRESS -p c=YTN

Miner:
https://github.com/JayDDee/cpuminer-opt/releases

Node:

addnode=103.232.209.140:9981
addnode=112.137.102.52:9981
addnode=121.83.83.246:9981
addnode=126.237.189.35:9981
addnode=133.130.107.34:9981
addnode=133.130.66.167:9981
addnode=150.95.185.164:9981
addnode=153.232.68.129:9981
addnode=160.16.72.64:9981
addnode=192.99.19.160:9981
addnode=203.189.97.135:9981
addnode=37.0.51.4:9981
addnode=80.209.234.38:9981
addnode=91.121.82.174:9981
addnode=91.69.247.135:9981

What yenten future? if community take over, Im in to project. lets vote and make community discord. please pm me.

[fred_handsome7]

shitcoin 

it is a disappointment to see a project with such huge potential die

[0xcitchx]

shitcoin 

it is a disappointment to see a project with such huge potential die

What yenten future? if community take over, Im in to project. lets vote and make community discord. please pm me.

[ptdvz]

please pm me.

Would have done so but you don't accept messages from newbies

[kage]

please pm me.

Would have done so but you don't accept messages from newbies

No need to be PM.  Put it down here for transparency so we can decide.

[ptdvz]

please pm me.

Would have done so but you don't accept messages from newbies

No need to be PM.  Put it down here for transparency so we can decide.

True. What i wanted to say is that i don't like discord but if he gets something going i'd support it. I mean at this point why not? This coin has quite a bit of community so why not put it to use?

[ohashi3d]

Now I'm trying solo-mining with v1.3.1 daemon...it's almost test-net...
My tweet, sorry in japanese, but you can see the screenshot of my private nomp pool:
https://twitter.com/ohashi3d/status/1053640382813106181

[ptdvz]

Now I'm trying solo-mining with v1.3.1 daemon...it's almost test-net...
My tweet, sorry in japanese, but you can see the screenshot of my private nomp pool:
https://twitter.com/ohashi3d/status/1053640382813106181

We truly seem to be living in interesting times...

This is what started in appearing lately in 1.3.1 node log:

Code:

CheckForkWarningConditions: Warning: Large valid fork found
  forking the chain at height 250675 (000032cc60c11c07cd6bae3f773834ef760fecd5b6baee9d1c0c7992b56e48b9)
  lasting to height 250695 (0000187e359816ff7f47138fbc502406909b9d49bb60df84be4ba3a3c548f5ce).
Chain state database corruption likely.

Node is at 250725 now but as you (or google translate) said that might be meaningless...

getinfo yields:

Code:

"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."