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

Arhgus

newbie

Activity: 199

Merit: 0

Quote from: LycheeBit on May 25, 2018, 11:28:37 AM

Yenten is available on LycheeBit mining pool
HAPPY MINING

MINING YENTEN WITH YESCRYPTR16 ALGO :

Stratum : lycheebit.com:6235
User : YOUR_YTN_ADDRESS
Password : c=YTN

LYCHEEBIT INFO :

Website : https://www.lycheebit.com/
Payout : Every hour
Fee : 1.00 %

MINING SOFTWARE :

CPU miner : https://github.com/JayDDee/cpuminer-opt/releases

EXAMPLES OF COMMAND LINE :

CPU Miner : cpuminer.exe -a yescryptr16 -o stratum+tcp://lycheebit.com:6235 -u YQhYUSxRMKSPagQFuL2imNzedGcv7pQW9x -p c=YTN

PEERS LIST :

addnode=51.15.58.122:9981
addnode=118.240.67.244:9981
addnode=71.13.237.197:9981
addnode=210.129.57.7:9981
addnode=193.70.33.8:9981
addnode=45.62.229.36:9981
addnode=47.94.45.200:9981
addnode=212.192.89.210:9981

great pool, thank you guys. highly recommend

Kgonla

newbie

Activity: 129

Merit: 0

Quote from: Xenon05 on June 03, 2018, 07:47:50 AM

Quote from: Kgonla on June 03, 2018, 07:36:57 AM

Quote from: Xenon05 on June 03, 2018, 06:04:08 AM

no sync of the wallet, o connection. even using this node from https://cryptoservices.net/en/nodes-yenten

addnode=154.49.213.96:9981
addnode=78.198.58.2:9981
addnode=51.15.58.122:9981
addnode=133.130.107.34:9981
addnode=150.95.173.81:9981
addnode=153.121.74.170:9981
addnode=210.129.57.7:9981
addnode=121.162.46.110:9981
addnode=109.226.212.183:9981

any help from the devs?

Latest wallet is not syncing from scratch.
You need to install v1.3 & when you are synced replace the exes with v2 ones.
Or wait for new release.

which exes to be replace, can you tell me how to?

Download the .zip for wallet v2.0.1
Inside there are 4 .exe files, just copy over the existing ones in the folder of v1.3.

Xenon05

jr. member

Activity: 228

Merit: 1

GPTCash Weekly Airdrop: https://discord.gg/RWPEsRa

Quote from: Kgonla on June 03, 2018, 07:36:57 AM

Quote from: Xenon05 on June 03, 2018, 06:04:08 AM

no sync of the wallet, o connection. even using this node from https://cryptoservices.net/en/nodes-yenten

addnode=154.49.213.96:9981
addnode=78.198.58.2:9981
addnode=51.15.58.122:9981
addnode=133.130.107.34:9981
addnode=150.95.173.81:9981
addnode=153.121.74.170:9981
addnode=210.129.57.7:9981
addnode=121.162.46.110:9981
addnode=109.226.212.183:9981

any help from the devs?

Latest wallet is not syncing from scratch.
You need to install v1.3 & when you are synced replace the exes with v2 ones.
Or wait for new release.

which exes to be replace, can you tell me how to?

Kgonla

newbie

Activity: 129

Merit: 0

Quote from: Xenon05 on June 03, 2018, 06:04:08 AM

no sync of the wallet, o connection. even using this node from https://cryptoservices.net/en/nodes-yenten

addnode=154.49.213.96:9981
addnode=78.198.58.2:9981
addnode=51.15.58.122:9981
addnode=133.130.107.34:9981
addnode=150.95.173.81:9981
addnode=153.121.74.170:9981
addnode=210.129.57.7:9981
addnode=121.162.46.110:9981
addnode=109.226.212.183:9981

any help from the devs?

Latest wallet is not syncing from scratch.
You need to install v1.3 & when you are synced replace the exes with v2 ones.
Or wait for new release.

Xenon05

jr. member

Activity: 228

Merit: 1

GPTCash Weekly Airdrop: https://discord.gg/RWPEsRa

no sync of the wallet, o connection. even using this node from https://cryptoservices.net/en/nodes-yenten

addnode=154.49.213.96:9981
addnode=78.198.58.2:9981
addnode=51.15.58.122:9981
addnode=133.130.107.34:9981
addnode=150.95.173.81:9981
addnode=153.121.74.170:9981
addnode=210.129.57.7:9981
addnode=121.162.46.110:9981
addnode=109.226.212.183:9981

any help from the devs?

trader1a

newbie

Activity: 41

Merit: 0

Quote from: stevascha on June 02, 2018, 02:29:02 PM

Quote from: Fast Fire Arrow on June 02, 2018, 12:33:55 PM

Hello. I installed the purse and it stuck for 3 days. Next, there is no synchronization. What's the problem, I do not know.
Synchronization lasts 72 hours...
Version Core: yenten_win64_2.0.1
https://s8.hostingkartinok.com/uploads/thumbs/2018/06/0bbf63de20bf8eac04c2416a02960823.png

https://s8.hostingkartinok.com/uploads/thumbs/2018/06/101026a9c32ebf203e7dcb22d004405f.png

yeah me too, it doesnt sync, do you have nodelist?

Here syncs ok, on ubuntu, 9 connections:
203.189.97.135:9981
94.41.49.197:9981
91.211.104.112:9981
133.130.66.167:9981
122.216.72.25:9981
58.191.220.12:9981
123.216.38.123:9981
222.12.98.40:9981
118.238.92.45:53404

stevascha

member

Activity: 312

Merit: 10

Quote from: Fast Fire Arrow on June 02, 2018, 12:33:55 PM

Hello. I installed the purse and it stuck for 3 days. Next, there is no synchronization. What's the problem, I do not know.
Synchronization lasts 72 hours...
Version Core: yenten_win64_2.0.1

yeah me too, it doesnt sync, do you have nodelist?

Fast Fire Arrow

jr. member

Activity: 145

Merit: 1

1BTC=$1 000 000,—I believe in it!

Hello. I installed the purse and it stuck for 3 days. Next, there is no synchronization. What's the problem, I do not know.
Synchronization lasts 72 hours...
Version Core: yenten_win64_2.0.1

bouldou

full member

Activity: 403

Merit: 101

Quote from: gabriel marces on June 01, 2018, 05:11:40 PM

What will happen within June ?)

?? What are you expecting to happend ??

In June, as in July, as for 10 years, we mine, mine, and mine again

bouldou

full member

Activity: 403

Merit: 101

Quote from: conan-equal-newone on May 31, 2018, 06:27:18 AM

v2.0.1 released.

maybe all pools and exchanges have to update...

BACKUP YOUR WALLET AND ANY FILES before updating from 1.3.1.

Wooowwww GREAT NEWS thank you Conan !! I've posted the news on our French crypto forum

Maybe you could "clean up" the first post now in the exchanges part !

gabriel marces

newbie

Activity: 13

Merit: 0

What will happen within June ?)

superman666

newbie

Activity: 84

Merit: 0

Yenten Core version v2.0.1.0-efd7833-dirty (64-bit) WORKING Grin

I'm using Win 2008 R2, first I replaced old exe files with new ones, the wallet synched after few hours.

https://i.imgur.com/FIVA2Fa.png

Kgonla

newbie

Activity: 129

Merit: 0

Yenten Core version v2.0.1.0-efd7833-dirty (64-bit) NOT WORKING

I'm using W7, first I replaced old files with new ones, the wallet was not starting.
I deleted old data & started syncing headers but stopped at 99.6%

https://fotos.subefotos.com/cb8baba63e81dbfee3e8d7975e3de915o.jpg

Code:

2018-06-01 08:39:20 Yenten version v2.0.1.0-efd7833-dirty
2018-06-01 08:39:20 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-06-01 08:39:20 Assuming ancestors of block 00001828d845205a951f9609e011775e035b00c7fb476310261ef30460cdccab have valid signatures.
2018-06-01 08:39:20 Setting nMinimumChainWork=000000000000000000000000000000000000000000000000000022334fa4b5fb
2018-06-01 08:39:20 Using the 'standard' SHA256 implementation
2018-06-01 08:39:20 Using RdRand as an additional entropy source
2018-06-01 08:39:22 Default data directory C:\Users\Administrador\AppData\Roaming\Yenten
2018-06-01 08:39:22 Using data directory C:\Program Files\yenten monedero
2018-06-01 08:39:22 Using config file C:\Program Files\yenten monedero\yenten.conf
2018-06-01 08:39:22 GUI: "registerShutdownBlockReason: Successfully registered: Yenten Core didn't yet exit safely..."
2018-06-01 08:39:22 Using at most 125 automatic connections (2048 file descriptors available)
2018-06-01 08:39:22 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2018-06-01 08:39:22 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-06-01 08:39:22 Using 2 threads for script verification
2018-06-01 08:39:22 init message: Verifying wallet(s)...
2018-06-01 08:39:22 scheduler thread start
2018-06-01 08:39:22 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-06-01 08:39:22 Using wallet wallet.dat
2018-06-01 08:39:22 CDBEnv::Open: LogDir=C:\Program Files\yenten monedero\database ErrorFile=C:\Program Files\yenten monedero\db.log
2018-06-01 08:39:22 Cache configuration:
2018-06-01 08:39:22 * Using 2.0MiB for block index database
2018-06-01 08:39:22 * Using 8.0MiB for chain state database
2018-06-01 08:39:22 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2018-06-01 08:39:22 init message: Loading block index...
2018-06-01 08:39:22 Opening LevelDB in C:\Program Files\yenten monedero\blocks\index
2018-06-01 08:39:22 Opened LevelDB successfully
2018-06-01 08:39:22 Using obfuscation key for C:\Program Files\yenten monedero\blocks\index: 0000000000000000
2018-06-01 08:39:22 Opening LevelDB in C:\Program Files\yenten monedero\hashes
2018-06-01 08:39:22 Opened LevelDB successfully
2018-06-01 08:39:22 Using obfuscation key for C:\Program Files\yenten monedero\hashes: 0000000000000000
2018-06-01 08:39:22 init message: Loading block index from disk...
2018-06-01 08:39:22 init message: Sorting block index...
2018-06-01 08:39:22 init message: Calculating nChainWork...
2018-06-01 08:39:22 LoadBlockIndexDB: last block file = 0
2018-06-01 08:39:22 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=268, heights=0...0, time=2017-10-03...2017-10-03)
2018-06-01 08:39:22 Checking all blk files are present...
2018-06-01 08:39:22 LoadBlockIndexDB: transaction index disabled
2018-06-01 08:39:22 Opening LevelDB in C:\Program Files\yenten monedero\chainstate
2018-06-01 08:39:22 Opened LevelDB successfully
2018-06-01 08:39:22 Using obfuscation key for C:\Program Files\yenten monedero\chainstate: 9816136143baf7b7
2018-06-01 08:39:22 Loaded best chain: hashBestChain=00001828d845205a951f9609e011775e035b00c7fb476310261ef30460cdccab height=0 date=2017-10-03 12:07:04 progress=0.000001
2018-06-01 08:39:22 init message: Rewinding blocks...
2018-06-01 08:39:22 init message: Verifying blocks...
2018-06-01 08:39:22  block index             124ms
2018-06-01 08:39:22 init message: Loading wallet...
2018-06-01 08:39:22 nFileVersion = 2000100
2018-06-01 08:39:22 Keys: 1001 plaintext, 0 encrypted, 1001 w/ metadata, 1001 total
2018-06-01 08:39:22  wallet                   28ms
2018-06-01 08:39:22 setKeyPool.size() = 1000
2018-06-01 08:39:22 mapWallet.size() = 18
2018-06-01 08:39:22 mapAddressBook.size() = 1
2018-06-01 08:39:22 mapBlockIndex.size() = 8001
2018-06-01 08:39:22 nBestHeight = 0
2018-06-01 08:39:22 Imported mempool transactions from disk: 0 successes, 0 failed, 0 expired
2018-06-01 08:39:22 torcontrol thread start
2018-06-01 08:39:22 upnp thread start
2018-06-01 08:39:22 Bound to [::]:9981
2018-06-01 08:39:22 Bound to 0.0.0.0:9981
2018-06-01 08:39:22 init message: Loading P2P addresses...
2018-06-01 08:39:22 Loaded 12477 addresses from peers.dat  61ms
2018-06-01 08:39:22 init message: Loading banlist...
2018-06-01 08:39:22 init message: Starting network threads...
2018-06-01 08:39:22 net thread start
2018-06-01 08:39:22 addcon thread start
2018-06-01 08:39:22 dnsseed thread start
2018-06-01 08:39:22 opencon thread start
2018-06-01 08:39:22 init message: Done loading
2018-06-01 08:39:22 msghand thread start
2018-06-01 08:39:22 GUI: Platform customization: "windows"
2018-06-01 08:39:22 GUI: PaymentServer::LoadRootCAs: Loaded  13  root certificates
2018-06-01 08:39:23 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152438, us=212.230.136.231:61566, peer=0
2018-06-01 08:39:30 No valid UPnP IGDs found
2018-06-01 08:39:30 upnp thread exit
2018-06-01 08:39:33 Loading addresses from DNS seeds (could take a while)
2018-06-01 08:39:33 0 addresses found from DNS seeds
2018-06-01 08:39:33 dnsseed thread exit
2018-06-01 08:40:20 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152438, us=212.230.136.231:61599, peer=1
2018-06-01 08:40:48 receive version message: /Satoshi:1.3.1/: version 70006, blocks=152438, us=212.230.136.231:61620, peer=2
2018-06-01 08:41:46 receive version message: /Satoshi:1.3.1/: version 70006, blocks=152438, us=212.230.136.231:61639, peer=3
2018-06-01 08:43:45 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152438, us=212.230.136.231:61671, peer=4
2018-06-01 08:50:53 Potential stale tip detected, will try using extra outbound peer (last tip update: 630 seconds ago)
2018-06-01 08:57:19 Timeout downloading headers from peer=0, disconnecting
2018-06-01 08:58:27 version handshake timeout from 5
2018-06-01 09:01:35 Potential stale tip detected, will try using extra outbound peer (last tip update: 1263 seconds ago)
2018-06-01 09:07:58 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152452, us=212.230.136.231:62007, peer=6
2018-06-01 09:12:14 Potential stale tip detected, will try using extra outbound peer (last tip update: 1905 seconds ago)
2018-06-01 09:15:00 Timeout downloading headers from peer=1, disconnecting
2018-06-01 09:15:51 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152457, us=212.230.136.231:62084, peer=7
2018-06-01 09:16:08 version handshake timeout from 7
2018-06-01 09:22:53 Potential stale tip detected, will try using extra outbound peer (last tip update: 2544 seconds ago)
2018-06-01 09:26:30 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152463, us=212.230.136.231:62201, peer=8
2018-06-01 09:32:40 Timeout downloading headers from peer=2, disconnecting
2018-06-01 09:33:31 Potential stale tip detected, will try using extra outbound peer (last tip update: 3183 seconds ago)
2018-06-01 09:34:07 socket recv error Se ha anulado una conexión establecida por el software en su equipo host..  (10053)
2018-06-01 09:34:35 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152469, us=212.230.136.231:62339, peer=10
2018-06-01 09:44:09 Potential stale tip detected, will try using extra outbound peer (last tip update: 3821 seconds ago)
2018-06-01 09:45:38 socket send error Se ha forzado la interrupción de una conexión existente por el host remoto.  (10054)
2018-06-01 09:49:53 Timeout downloading headers from peer=4, disconnecting
2018-06-01 09:50:31 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152478, us=212.230.136.231:62488, peer=12
2018-06-01 09:50:56 version handshake timeout from 12
2018-06-01 09:54:40 Potential stale tip detected, will try using extra outbound peer (last tip update: 4459 seconds ago)
2018-06-01 09:55:51 ping timeout: 1200.005638s
2018-06-01 09:56:24 receive version message: /Satoshi:1.3.1/: version 70006, blocks=152481, us=212.230.136.231:62550, peer=13
2018-06-01 09:57:11 socket recv error Se ha anulado una conexión establecida por el software en su equipo host..  (10053)
2018-06-01 09:57:21 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152482, us=212.230.136.231:62557, peer=15
2018-06-01 10:05:12 Potential stale tip detected, will try using extra outbound peer (last tip update: 5090 seconds ago)
2018-06-01 10:07:07 Timeout downloading headers from peer=6, disconnecting
2018-06-01 10:07:30 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152484, us=212.230.136.231:62647, peer=16
2018-06-01 10:15:43 Potential stale tip detected, will try using extra outbound peer (last tip update: 5722 seconds ago)
2018-06-01 10:24:30 Timeout downloading headers from peer=10, disconnecting
2018-06-01 10:25:28 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152490, us=212.230.136.231:62803, peer=17
2018-06-01 10:26:14 Potential stale tip detected, will try using extra outbound peer (last tip update: 6353 seconds ago)
2018-06-01 10:27:06 socket recv error Se ha anulado una conexión establecida por el software en su equipo host..  (10053)
2018-06-01 10:36:44 Potential stale tip detected, will try using extra outbound peer (last tip update: 6984 seconds ago)
2018-06-01 10:38:39 socket recv error Se ha anulado una conexión establecida por el software en su equipo host..  (10053)
2018-06-01 10:41:30 Timeout downloading headers from peer=8, disconnecting
2018-06-01 10:42:05 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152502, us=212.230.136.231:62998, peer=20
2018-06-01 10:47:14 Potential stale tip detected, will try using extra outbound peer (last tip update: 7614 seconds ago)
2018-06-01 10:57:44 Potential stale tip detected, will try using extra outbound peer (last tip update: 8244 seconds ago)
2018-06-01 10:58:19 Timeout downloading headers from peer=16, disconnecting
2018-06-01 10:58:53 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152513, us=212.230.136.231:63142, peer=21
2018-06-01 11:05:30 socket recv error Se ha anulado una conexión establecida por el software en su equipo host..  (10053)
2018-06-01 11:08:14 Potential stale tip detected, will try using extra outbound peer (last tip update: 8874 seconds ago)
2018-06-01 11:14:56 Timeout downloading headers from peer=13, disconnecting
2018-06-01 11:18:45 Potential stale tip detected, will try using extra outbound peer (last tip update: 9504 seconds ago)
2018-06-01 11:25:49 socket recv error Se ha anulado una conexión establecida por el software en su equipo host..  (10053)
2018-06-01 11:29:15 Potential stale tip detected, will try using extra outbound peer (last tip update: 10135 seconds ago)
2018-06-01 11:31:22 Timeout downloading headers from peer=20, disconnecting
2018-06-01 11:31:45 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152527, us=212.230.136.231:63489, peer=24
2018-06-01 11:37:25 ping timeout: 1200.045918s
2018-06-01 11:38:04 receive version message: /Satoshi:1.3.1/: version 70006, blocks=152531, us=212.230.136.231:63554, peer=25
2018-06-01 11:38:27 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152531, us=212.230.136.231:63556, peer=26
2018-06-01 11:39:48 Potential stale tip detected, will try using extra outbound peer (last tip update: 10766 seconds ago)
2018-06-01 11:47:50 Timeout downloading headers from peer=17, disconnecting
2018-06-01 11:48:48 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152533, us=212.230.136.231:63662, peer=27
2018-06-01 11:48:54 version handshake timeout from 27
2018-06-01 11:50:19 Potential stale tip detected, will try using extra outbound peer (last tip update: 11398 seconds ago)
2018-06-01 11:53:46 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152537, us=212.230.136.231:63738, peer=28
2018-06-01 11:58:32 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152538, us=212.230.136.231:63814, peer=29
2018-06-01 12:00:50 Potential stale tip detected, will try using extra outbound peer (last tip update: 12029 seconds ago)
2018-06-01 12:04:05 Timeout downloading headers from peer=25, disconnecting
2018-06-01 12:11:20 Potential stale tip detected, will try using extra outbound peer (last tip update: 12660 seconds ago)
2018-06-01 12:20:08 Timeout downloading headers from peer=24, disconnecting
2018-06-01 12:20:53 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152552, us=212.230.136.231:64090, peer=30
2018-06-01 12:21:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 13290 seconds ago)
2018-06-01 12:29:03 ping timeout: 1200.009001s
2018-06-01 12:29:52 Pre-allocating up to position 0x100000 in rev00000.dat
2018-06-01 12:29:52 UpdateTip: new best=00002c6699e7066573faad775e7f1a6a432b902a1f4424af25dc6f8d6b9b8ba7 height=1 version=0x00000002 log2_work=19 tx=2 date='2017-10-28 19:21:01' progress=0.000001 cache=0.0MiB(1txo)
2018-06-01 12:29:53 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152554, us=212.230.136.231:64219, peer=31
2018-06-01 12:30:04 UpdateTip: new best=0000250f4c74f4fd0b1a31cff679250ba01095e34b34d8f5445b31712a18fa4b height=2 version=0x00000002 log2_work=19.584963 tx=3 date='2017-10-28 19:24:15' progress=0.000002 cache=0.0MiB(2txo)
2018-06-01 12:30:16 UpdateTip: new best=000033a06900b30aeab143701bc24891aa4785e1748363dc04105c4e16fcf117 height=3 version=0x00000002 log2_work=20 tx=4 date='2017-10-28 19:26:03' progress=0.000003 cache=0.0MiB(3txo)
2018-06-01 12:30:27 ERROR: AcceptBlock: bad-cb-height, block height mismatch in coinbase (code 16)
2018-06-01 12:30:27 Misbehaving: 122.216.72.25:9981 peer=30 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-06-01 12:30:27 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-06-01 12:31:24 Timeout downloading block 0000095cbce2ac764515575e10964d595349440ac9fc89be908f4126479901c6 from peer=29, disconnecting
2018-06-01 12:31:36 Timeout downloading block 000008e5db1a0f418eb58d93885101a71d8370ee3c0f899ec38bd105caea2740 from peer=28, disconnecting
2018-06-01 12:31:54 receive version message: /Satoshi:1.3.1/: version 70006, blocks=152554, us=212.230.136.231:64237, peer=32
2018-06-01 12:32:17 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152554, us=212.230.136.231:64246, peer=33
2018-06-01 12:32:28 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152554, us=212.230.136.231:64247, peer=34
2018-06-01 12:43:05 Potential stale tip detected, will try using extra outbound peer (last tip update: 762 seconds ago)
2018-06-01 12:53:35 Potential stale tip detected, will try using extra outbound peer (last tip update: 1399 seconds ago)
2018-06-01 13:04:05 Potential stale tip detected, will try using extra outbound peer (last tip update: 2029 seconds ago)
2018-06-01 13:14:35 Potential stale tip detected, will try using extra outbound peer (last tip update: 2659 seconds ago)
2018-06-01 13:24:47 receive version message: /Satoshi:2.0.1/: version 70015, blocks=3, us=212.230.136.231:64805, peer=35
2018-06-01 13:25:05 Potential stale tip detected, will try using extra outbound peer (last tip update: 3289 seconds ago)
2018-06-01 13:30:06 receive version message: /Satoshi:2.0.1/: version 70015, blocks=3, us=212.230.136.231:64859, peer=36
2018-06-01 13:35:35 Potential stale tip detected, will try using extra outbound peer (last tip update: 3919 seconds ago)
2018-06-01 13:41:05 receive version message: /Satoshi:2.0.1/: version 70015, blocks=3, us=212.230.136.231:64958, peer=37
2018-06-01 13:42:56 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152592, us=212.230.136.231:64995, peer=38
2018-06-01 13:46:05 Potential stale tip detected, will try using extra outbound peer (last tip update: 4549 seconds ago)
2018-06-01 13:56:35 Potential stale tip detected, will try using extra outbound peer (last tip update: 5179 seconds ago)
2018-06-01 14:00:43 receive version message: /Satoshi:2.0.1/: version 70015, blocks=3, us=212.230.136.231:65208, peer=40
2018-06-01 14:07:05 Potential stale tip detected, will try using extra outbound peer (last tip update: 5809 seconds ago)
2018-06-01 14:15:03 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152604, us=212.230.136.231:65371, peer=41
2018-06-01 14:17:35 Potential stale tip detected, will try using extra outbound peer (last tip update: 6439 seconds ago)
2018-06-01 14:21:19 socket recv error Se ha anulado una conexión establecida por el software en su equipo host..  (10053)
2018-06-01 14:22:45 Disconnecting outbound peer 40 for old chain, best known block = 
2018-06-01 14:28:05 Potential stale tip detected, will try using extra outbound peer (last tip update: 7069 seconds ago)
2018-06-01 14:32:56 receive version message: /Satoshi:2.0.1/: version 70015, blocks=3, us=212.230.136.231:49249, peer=44
2018-06-01 14:33:41 receive version message: /Satoshi:1.3.1/: version 70006, blocks=152615, us=212.230.136.231:49258, peer=45
2018-06-01 14:38:35 Potential stale tip detected, will try using extra outbound peer (last tip update: 7699 seconds ago)
2018-06-01 14:49:05 Potential stale tip detected, will try using extra outbound peer (last tip update: 8329 seconds ago)
2018-06-01 14:54:58 Disconnecting outbound peer 44 for old chain, best known block = 
2018-06-01 14:56:00 receive version message: /Satoshi:2.0.1/: version 70015, blocks=3, us=212.230.136.231:49540, peer=46
2018-06-01 14:59:35 Potential stale tip detected, will try using extra outbound peer (last tip update: 8959 seconds ago)
2018-06-01 15:10:05 Potential stale tip detected, will try using extra outbound peer (last tip update: 9589 seconds ago)
2018-06-01 15:18:02 Disconnecting outbound peer 46 for old chain, best known block = 
2018-06-01 15:20:35 Potential stale tip detected, will try using extra outbound peer (last tip update: 10219 seconds ago)
2018-06-01 15:28:07 receive version message: /Satoshi:2.0.1/: version 70015, blocks=3, us=212.230.136.231:49886, peer=48
2018-06-01 15:31:05 Potential stale tip detected, will try using extra outbound peer (last tip update: 10849 seconds ago)
2018-06-01 15:35:24 socket recv error Se ha anulado una conexión establecida por el software en su equipo host..  (10053)
2018-06-01 15:36:00 socket recv error Se ha anulado una conexión establecida por el software en su equipo host..  (10053)
2018-06-01 15:38:01 socket recv error Se ha anulado una conexión establecida por el software en su equipo host..  (10053)
2018-06-01 15:41:35 Potential stale tip detected, will try using extra outbound peer (last tip update: 11479 seconds ago)
2018-06-01 15:47:48 receive version message: /Satoshi:2.0.1/: version 70015, blocks=152651, us=212.230.136.231:50109, peer=53
2018-06-01 15:50:33 receive version message: /Satoshi:2.0.1/: version 70015, blocks=3, us=212.230.136.231:50147, peer=54
2018-06-01 15:52:05 Potential stale tip detected, will try using extra outbound peer (last tip update: 12109 seconds ago)
2018-06-01 16:02:35 Potential stale tip detected, will try using extra outbound peer (last tip update: 12739 seconds ago)
2018-06-01 16:13:05 Potential stale tip detected, will try using extra outbound peer (last tip update: 13369 seconds ago)
2018-06-01 16:23:35 Potential stale tip detected, will try using extra outbound peer (last tip update: 13999 seconds ago)
2018-06-01 16:34:05 Potential stale tip detected, will try using extra outbound peer (last tip update: 14629 seconds ago)
2018-06-01 16:44:35 Potential stale tip detected, will try using extra outbound peer (last tip update: 15259 seconds ago)
2018-06-01 16:48:23 receive version message: /Satoshi:2.0.1/: version 70015, blocks=0, us=212.230.136.231:50853, peer=60
2018-06-01 16:55:05 Potential stale tip detected, will try using extra outbound peer (last tip update: 15889 seconds ago)
2018-06-01 17:05:35 Potential stale tip detected, will try using extra outbound peer (last tip update: 16519 seconds ago)
2018-06-01 17:10:25 Disconnecting outbound peer 60 for old chain, best known block = 
2018-06-01 17:16:06 Potential stale tip detected, will try using extra outbound peer (last tip update: 17150 seconds ago)
2018-06-01 17:21:06 receive version message: /Satoshi:2.0.1/: version 70015, blocks=0, us=212.230.136.231:51170, peer=62
2018-06-01 17:26:36 Potential stale tip detected, will try using extra outbound peer (last tip update: 17780 seconds ago)
2018-06-01 17:37:06 Potential stale tip detected, will try using extra outbound peer (last tip update: 18410 seconds ago)
2018-06-01 17:43:08 Disconnecting outbound peer 62 for old chain, best known block = 
2018-06-01 17:43:33 receive version message: /Satoshi:2.0.1/: version 70015, blocks=0, us=212.230.136.231:51407, peer=63
2018-06-01 17:47:36 Potential stale tip detected, will try using extra outbound peer (last tip update: 19040 seconds ago)
2018-06-01 17:58:06 Potential stale tip detected, will try using extra outbound peer (last tip update: 19670 seconds ago)
2018-06-01 18:05:35 Disconnecting outbound peer 63 for old chain, best known block = 
2018-06-01 18:06:07 receive version message: /Satoshi:2.0.1/: version 70015, blocks=0, us=212.230.136.231:51624, peer=64
2018-06-01 18:08:36 Potential stale tip detected, will try using extra outbound peer (last tip update: 20300 seconds ago)
2018-06-01 18:12:14 receive version message: /Satoshi:2.0.1/: version 70015, blocks=0, us=212.230.136.231:51698, peer=65

lam06061999

newbie

Activity: 26

Merit: 0

Is there some discord or something like that? I dont find it on first page.

Earl_Vadim

jr. member

Activity: 125

Merit: 2

COINSTOCK
Cryptocurrency Exchange with fiat

The Taler-EX.online will be close soon... Exchange is rebranded and migrate to new platform https://coinstock.me
Yenten listed with BTC, USD, TLR

cozzz

newbie

Activity: 11

Merit: 0

Quote from: SquealerFin on May 31, 2018, 02:53:21 PM

Hello!

I have Yenten core v1.2.1.0-f93d599-beta.
How can I update to the latest version....do i have to import private keys from my addresses or what?

Do you have wallet.dat? On windows 7, it is in C:\Users\\AppData\Roaming\Yenten.
If you have it, backup the Yenten folder before. After backup, you can start new Yenten core.

But you have only private keys, you can use importprivkey command in the Console.
Start new Yenten core. Select Debug window in Help menu.
On Debug window click on Console tab and type the command importprivkey

Code:

importprivkey

SquealerFin

newbie

Activity: 11

Merit: 0

Hello!

I have Yenten core v1.2.1.0-f93d599-beta.
How can I update to the latest version....do i have to import private keys from my addresses or what?

para_gon

newbie

Activity: 17

Merit: 0

price YTN increases

andronikos

full member

Activity: 336

Merit: 101

Quote from: conan-equal-newone on May 31, 2018, 06:27:18 AM

v2.0.1 released.

maybe all pools and exchanges have to update...

BACKUP YOUR WALLET AND ANY FILES before updating from 1.3.1.

Nice Work. Thank you Grin

ohashi3d

jr. member

Activity: 51

Merit: 3

Quote from: cpu-pool on May 31, 2018, 02:50:22 AM

Quote from: cpu-pool on May 30, 2018, 04:08:22 AM

CPU-POOL - pool for mining on cpu coins

http://cpu-pool.com/ - convenient, without registration, for weak and powerful processors, adaptive complexity of hashes (diff 0.1-0.5)

p.s. who will find the first block - 30 Yentens as a gift!!!

Congratulations - YQqFKoc8t7QcBH2Sg8h9SecYBkQAkzxABa.CPU1 found the first BLOCK in 2018-05-30 21:33
We send him 30 Yenten. Well done !!! (Yentens will soon come;))

p.s. There were errors in the frontend, the block was not displayed, the error has already been fixed.

Hi,

Congratulations, 1st block and Yenten 2.0.1!!!
...I'm a newbie from Japan, just registered on Bitcointalk today Wink

I've confirmed your 30YTN gift, THANKS

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