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

netto7

jr. member

Activity: 252

Merit: 4

today price drop to 36sat

qwaver

newbie

Activity: 31

Merit: 0

Quote from: AlecMe on October 19, 2018, 03:05:45 AM

discord channel?

https://discord.gg/eE7Yp2h

AlecMe

full member

Activity: 392

Merit: 159

discord channel?

Disallowedword

newbie

Activity: 115

Merit: 0

Quote from: tross on October 18, 2018, 01:15:42 PM

http://cpumining.zapto.org/

Now offering Elicoin and Yenten!

0% fee till Monday!

Code:

cpuminer-sse2.exe -a yescryptR16 -o stratum+tcp://cpumining.zapto.org:6337 -u YENTEN WALLET -p c=YTN -t 4

Code:

cpuminer-sse2.exe -a yescryptR16 -o stratum+tcp://cpumining.zapto.org:6334 -u ELICOIN WALLET -p c=ELI -t 4

DISCORD
https://discord.gg/AtPzmxC
POOL
http://cpumining.zapto.org/

Disallowedword

newbie

Activity: 115

Merit: 0

Quote from: guny on October 12, 2018, 10:53:44 AM

Quote from: Guzek71 on October 12, 2018, 02:19:36 AM

######## 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.

tross

member

Activity: 112

Merit: 10

http://cpumining.zapto.org/

Now offering Elicoin and Yenten!

0% fee till Monday!

Code:

cpuminer-sse2.exe -a yescryptR16 -o stratum+tcp://cpumining.zapto.org:6337 -u YENTEN WALLET -p c=YTN -t 4

Code:

cpuminer-sse2.exe -a yescryptR16 -o stratum+tcp://cpumining.zapto.org:6334 -u ELICOIN WALLET -p c=ELI -t 4

DISCORD
https://discord.gg/AtPzmxC
POOL
http://cpumining.zapto.org/

malegeo

newbie

Activity: 1

Merit: 0

The reason Conan not show up, is because it is a scam and if you want to know more, check Wavi coin.
Developer already cash out and leave newbies with big bag.
Yenten bag holders are now try to runaway and cash out at lose.
The real value of Yenten is 0 sat
I predict delist will happen where soon.

Guzek71

newbie

Activity: 6

Merit: 0

I just sold my 75k Yenten.
Very disappointing how this coin end.
Better for everyone to move your CPU power to other coins.

ohashi3d

jr. member

Activity: 51

Merit: 3

Quote from: pikosan on October 18, 2018, 05:21:05 AM

Use the Debug window command:{getblockhash "height"} on the Official 2.0.1fix wallet, I find the hash of block 248958 and block 248959 is the same with your debug.log of CVE-2018-17144-fixed wallet.

Yeah, these were obtained with the Official 2.0.1fix wallet:
block 248958: 0000002390e6be74008db3fd88a144657de442cf03f72e9f8a2e446fd6f304f1
block 248959: 00000015b1fa187ffdc1bd7c16dea391702b58b765bf50433dd1666ca2d3973e
I'm curious what version is running on https://ytn.overemo.com/...

And my CVE-2018-17144-fixed wallet got stuck again at block height 250704:
...
2018-10-18 04:23:21 UpdateTip: new best=000000224d12ce6300e18f44e5fa449bc1f7185deab6cca655213c9dab468f34 height=250704 version=0x20000001 log2_work=45.524203 tx=1109470 date='2018-10-18 04:22:51' progress=0.999998 cache=0.4MiB(2897txo)
2018-10-18 04:23:21 connect() to 195.201.212.26:9981 failed after select(): Connection refused (111)
2018-10-18 04:24:23 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-10-18 04:24:28 Misbehaving: 85.175.30.184:54303 peer=736 (0 -> 100) BAN THRESHOLD EXCEEDED
...
Still, after syncing with the original 2.0.1-fix wallet, my CVE-2018-17144-fixed wallet got into running again...

I'm not sure whether it's a result of attack or not, but anyway it looks chaotic, endless battle...

pikosan

newbie

Activity: 9

Merit: 0

Quote from: ohashi3d on October 17, 2018, 06:49:38 PM

CVE-2018-17144-fixed wallet stopped accepting blocks at height 248957.
In my debug.log:

...
2018-10-15 17:11:09 UpdateTip: new best=00000007876142530eaeca32e71d38179480cbebc45fe964fbe0c3e84b012493 height=248957 version=0x20000001 log2_work=45.519688 tx=1106206 date='2018-10-15 17:10:23' progress=0.999997 cache=0.7MiB(5617txo)
2018-10-15 17:11:09 CreateNewBlock(): block weight: 12110 txs: 26 fees: 240000 sigops 504
2018-10-15 17:11:15 CreateNewBlock(): block weight: 12560 txs: 27 fees: 314777 sigops 508
2018-10-15 17:11:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-10-15 17:11:32 Misbehaving: 185.185.69.156:9981 peer=2 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-10-15 17:11:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-10-15 17:11:33 Misbehaving: 212.192.89.210:9981 peer=3 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-10-15 17:11:33 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-10-15 17:11:33 receive version message: /Satoshi:2.0.1/: version 70015, blocks=248958, us=180.42.175.133:41346, peer=87
...

"AcceptBlock FAILED" message is defined in 'ProcessNewBlock' function, in validation.cpp.
'ProcessNewBlock' function calls 'CheckBlock' function, and Fix for CVE-2018-17144 is enabling a check in 'CheckBlock' function.
So...my guess is, there was a attack attempt related to CVE-2018-17144 on Oct. 15th.
I think running CVE-2018-17144-fixed wallets is very very very few, so the fixed wallets were banned...

The original 2.0.1-fix wallet looks working as usual, and once synced with the original wallet,
CVE-2018-17144-fixed wallet works again, at least at this moment.
But while CVE-2018-17144-fixed wallets aren't in the majority, fixed wallets will be banned again in the next attack...
I think this situation will not change easily...

Another supporting evidence of attack attempt:

The Yenten exploer https://ytn.overemo.com/ shows:

block 248957: Block hash: 00000007876142530eaeca32e71d38179480cbebc45fe964fbe0c3e84b012493
block 248958: Block hash: 00000022193d53b1aa17ac7b86fce2ceecbaba36f0e6d2a0a483c227d7aa4d67
block 248959: Block hash: 00000013b54daf77086e740d4e0d7721afd933614c84321c54d2f4d85e553d42

The hash of 248957 is same as my debug.log by logged with the CVE-2018-17144-fixed wallet,
but 248958 and 248959 are different from the value by logged with the original 2.0.1-fix wallet:
block 248958: 0000002390e6be74008db3fd88a144657de442cf03f72e9f8a2e446fd6f304f1
block 248959: 00000015b1fa187ffdc1bd7c16dea391702b58b765bf50433dd1666ca2d3973e

BTW, though I'm a Japanese, the Yenten Disccrd is not comfortable for me, at this moment, unfortunately...
I may upload Windows binary of CVE-2018-17144-fixed wallet stamped with version 2.0.2 on GitHub, of my own will,
but also I may delete them, of my own will.

Use the Debug window command:{getblockhash "height"} on the Official 2.0.1fix wallet, I find the hash of block 248958 and block 248959 is the same with your debug.log of CVE-2018-17144-fixed wallet.

tross

member

Activity: 112

Merit: 10

http://cpumining.zapto.org/

Now offering Elicoin and Yenten!

Code:

cpuminer-sse2.exe -a yescryptR16 -o stratum+tcp://cpumining.zapto.org:6337 -u YENTEN WALLET -p c=YTN -t 4

Code:

cpuminer-sse2.exe -a yescryptR16 -o stratum+tcp://cpumining.zapto.org:6334 -u ELICOIN WALLET -p c=ELI -t 4

DISCORD
https://discord.gg/AtPzmxC
POOL
http://cpumining.zapto.org/

L0G1C

newbie

Activity: 36

Merit: 0

I also get kicked from their discord for no reason!

ohashi3d

jr. member

Activity: 51

Merit: 3

CVE-2018-17144-fixed wallet stopped accepting blocks at height 248957.
In my debug.log:

...
2018-10-15 17:11:09 UpdateTip: new best=00000007876142530eaeca32e71d38179480cbebc45fe964fbe0c3e84b012493 height=248957 version=0x20000001 log2_work=45.519688 tx=1106206 date='2018-10-15 17:10:23' progress=0.999997 cache=0.7MiB(5617txo)
2018-10-15 17:11:09 CreateNewBlock(): block weight: 12110 txs: 26 fees: 240000 sigops 504
2018-10-15 17:11:15 CreateNewBlock(): block weight: 12560 txs: 27 fees: 314777 sigops 508
2018-10-15 17:11:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-10-15 17:11:32 Misbehaving: 185.185.69.156:9981 peer=2 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-10-15 17:11:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-10-15 17:11:33 Misbehaving: 212.192.89.210:9981 peer=3 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-10-15 17:11:33 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-10-15 17:11:33 receive version message: /Satoshi:2.0.1/: version 70015, blocks=248958, us=180.42.175.133:41346, peer=87
...

"AcceptBlock FAILED" message is defined in 'ProcessNewBlock' function, in validation.cpp.
'ProcessNewBlock' function calls 'CheckBlock' function, and Fix for CVE-2018-17144 is enabling a check in 'CheckBlock' function.
So...my guess is, there was a attack attempt related to CVE-2018-17144 on Oct. 15th.
I think running CVE-2018-17144-fixed wallets is very very very few, so the fixed wallets were banned...

The original 2.0.1-fix wallet looks working as usual, and once synced with the original wallet,
CVE-2018-17144-fixed wallet works again, at least at this moment.
But while CVE-2018-17144-fixed wallets aren't in the majority, fixed wallets will be banned again in the next attack...
I think this situation will not change easily...

Another supporting evidence of attack attempt:

The Yenten exploer https://ytn.overemo.com/ shows:

block 248957: Block hash: 00000007876142530eaeca32e71d38179480cbebc45fe964fbe0c3e84b012493
block 248958: Block hash: 00000022193d53b1aa17ac7b86fce2ceecbaba36f0e6d2a0a483c227d7aa4d67
block 248959: Block hash: 00000013b54daf77086e740d4e0d7721afd933614c84321c54d2f4d85e553d42

The hash of 248957 is same as my debug.log by logged with the CVE-2018-17144-fixed wallet,
but 248958 and 248959 are different from the value by logged with the original 2.0.1-fix wallet:
block 248958: 0000002390e6be74008db3fd88a144657de442cf03f72e9f8a2e446fd6f304f1
block 248959: 00000015b1fa187ffdc1bd7c16dea391702b58b765bf50433dd1666ca2d3973e

BTW, though I'm a Japanese, the Yenten Disccrd is not comfortable for me, at this moment, unfortunately...
I may upload Windows binary of CVE-2018-17144-fixed wallet stamped with version 2.0.2 on GitHub, of my own will,
but also I may delete them, of my own will.

graviex

member

Activity: 628

Merit: 10

New exchange generation

Graviex exchange updated wallet to 2.0.1 version. https://graviex.net/wallets/list#

Wellcome to trade https://graviex.net/markets/ytnbtc?pinned=true

FacelessCrypto

full member

Activity: 539

Merit: 105

IDENA.IO - Proof-Of-Person Blockchain

Stayvwith wallet 1.xxx

ashguine

newbie

Activity: 65

Merit: 0

The CVE-2018-17144 prepared wallet created by the community has been refused connection from the network since 08: 10 UTC on October 16, 2018.
If there is a problem with syncing with Wallet, we recommend you to return to Official Wallet v 2.0.1fix.
https://github.com/conan-equal-newone/yenten/releases

If you can not synchronize with v2.0.1, please use Fast-Yenten to install a new one.
Please put Wallet.dat in C:\yenten\data
Fast-yenten https://bitcointalksearch.org/topic/m.44405573

Please make a backup of Wallet's change carefully.

Arhgus

newbie

Activity: 199

Merit: 0

Quote from: Lind on October 16, 2018, 06:38:39 AM

Quote from: FacelessCrypto on October 16, 2018, 12:56:20 AM

Is developer alive? Conan is Mr. Mask and so Boone know the date of real developer.. it's been a while he logged in Bitcoin talk

Network seems to have some issues now lol, missing dev and bad wallet.

I declare this stuff dead as the others. If this thing looses the working chain, its last and only good point, then it is good as dead. Roll Eyes

I do not think so, there is a revival in the market, someone is buying up coins. ytn good coin, the chain is normal everything works like a clock

Lind

member

Activity: 328

Merit: 27

Quote from: FacelessCrypto on October 16, 2018, 12:56:20 AM

Is developer alive? Conan is Mr. Mask and so Boone know the date of real developer.. it's been a while he logged in Bitcoin talk

Network seems to have some issues now lol, missing dev and bad wallet.

I declare this stuff dead as the others. If this thing looses the working chain, its last and only good point, then it is good as dead. Roll Eyes

FacelessCrypto

full member

Activity: 539

Merit: 105

IDENA.IO - Proof-Of-Person Blockchain

Is developer alive? Conan is Mr. Mask and so Boone know the date of real developer.. it's been a while he logged in Bitcoin talk

ashguine

newbie

Activity: 65

Merit: 0

https://i.imgur.com/nT0Ged9.jpg

Topic: [ANN] [CPU mining] Yenten v2.0.1 [YTN] [YescryptR16] [Exchange avilable] - page 19. (Read 147137 times)