Author

Topic: [ANN][XMY] Myriad | Multi-Algo, Fair, Secure - page 102. (Read 850158 times)

full member
Activity: 204
Merit: 100
There are currently quite a few forks on the network unfortunately...

Do we know what pools are on the correct forks and which algo is correct?

OC,

Is your mry-gro pool on correct fork?



with today work here:
http://myriad.p2pool.geek.nz

for Myr-Groestl lot happens stale  Huh
holiday "low diff" in Groestl continues ))
legendary
Activity: 1400
Merit: 1000
There are currently quite a few forks on the network unfortunately...

Do we know what pools are on the correct forks and which algo is correct?

OC,

Is your mry-gro pool on correct fork?



Just checked and both pools are on the correct fork, myrgrs.suprnova.cc and myrq.suprnova.cc

OC,

You the man.
legendary
Activity: 2716
Merit: 1240
There are currently quite a few forks on the network unfortunately...

Do we know what pools are on the correct forks and which algo is correct?

OC,

Is your mry-gro pool on correct fork?



Just checked and both pools are on the correct fork, myrgrs.suprnova.cc and myrq.suprnova.cc
legendary
Activity: 1400
Merit: 1000
There are currently quite a few forks on the network unfortunately...

Do we know what pools are on the correct forks and which algo is correct?

OC,

Is your mry-gro pool on correct fork?

full member
Activity: 146
Merit: 100
There are currently quite a few forks on the network unfortunately...

This should be the correct fork:

Code:
myriadcoind getblockhash 752694
ae1ce01cc9a8765b9853b8ecf24179bedbc84f11b689538b1adee376ca4540b6
member
Activity: 102
Merit: 10
I don't know how I feel about sharing an about to explode currency with a cheating asshole who might dump everything at slightest price jump.
Makes me uneasy.
legendary
Activity: 2716
Merit: 1240
There are currently quite a few forks on the network unfortunately...
full member
Activity: 204
Merit: 100

lost some incoming transactions

messages come without coins
legendary
Activity: 2716
Merit: 1240
I've updated the Suprnova Pools to the new Release.
full member
Activity: 204
Merit: 100
ok

Debian 6 amd64
build:

./configure --enable-tests=no --with-miniupnpc
make
start myriadcoin-qt
all good ))
full member
Activity: 146
Merit: 100
Required update

Please update to version 0.9.2.7 before block 766000. Block 76600 should be reached in 2 to 4 days.

This version improves on time warp attack mitigation:

1. Only 3 blocks from the same algo will now be allowed consecutively (previously this was 6).
2. Difficulty will adjust maximum 4% up and 4% down (previously 2% up and 4% down).
3. Improvement to invalid block time detection

Thank you for your patience and support.



Github source
http://github.com/myriadcoin/myriadcoin


Windows wallet
0.9.2.7 (latest release)
Win32
https://mega.co.nz/#!U452lJrB!PionXwPZThYjH4depmX01QYIh0LP759qisq-UsC0Rcg
https://www.dropbox.com/s/kt0uqnmjremn061/myriadcoin.0.9.2.7.win32.zip?dl=0

Win64
https://mega.co.nz/#!Bxhy3RST!lGxCMhD_IJQTz_6ZOjYDAR3eupKzMy6QqmgxhKROOF8
https://www.dropbox.com/s/8n8ellimq8kuit4/myriadcoin.0.9.2.7.win64.zip?dl=0
member
Activity: 94
Merit: 10
Um, is it just my imagination, or is Groestl finding a boatload of blocks again today?

Check out http://birdonwheels5.no-ip.org:3000/.

Yes, the attacker is back. He is much less effective this time compared to last time, due to our improved counter measures.

I plan to improve on these counter measures in a new release soon.


4 blocks/minute is still a LOT of MYR to be getting away with.  Hope you get the fix out soon!
full member
Activity: 146
Merit: 100
Um, is it just my imagination, or is Groestl finding a boatload of blocks again today?

Check out http://birdonwheels5.no-ip.org:3000/.

Yes, the attacker is back. He is much less effective this time compared to last time, due to our improved counter measures.

I plan to improve on these counter measures in a new release soon.
legendary
Activity: 3178
Merit: 1119
Um, is it just my imagination, or is Groestl finding a boatload of blocks again today?

Check out http://birdonwheels5.no-ip.org:3000/.


No, seems legit. I haven't checked myself, but saw this conversation on IRC over the last hour:

Quote
[07:56:11] hi guys
[08:06:22] howdy
[08:43:04] i plan on bringing out a new version soon that will further strengthen against attacks
[08:46:16] how come so many more groestl blocks are being solved compared to the other algos
[08:46:19] http://birdonwheels5.no-ip.org/blocks
[08:46:45] its 6 groestl blocks, 1 sha/scrypt/qubit/skein and then 6 more groestl
[08:47:40] http://myriad.theblockexplorer.com/temp.php
[08:47:50] larraboj: yes, that is one of our security measures kicking in. somebody is attempting to manipulate groestl again to get more blocks.
[08:48:41] is it because the groestl hashrate is not high enough?
[08:49:20] groestl is the easiest target because it has the lowest hash. they are sending fake data in their groestl blocks to try and manipulate the groestl diff further down.
[08:50:41] when they previously tried this attack they managed to get got around 50 blocks a minute.. now around 4 a minute. i plan to tighten this security further.
[08:54:51] --> Vit_ (b025640e@gateway/web/freenode/ip.176.37.100.14) has joined ##myriadcoin
[08:58:53] I thought only being able to solve 6 blocks in a row would make the time warp attack more difficult

So, hopefully we'll see another update in the next day or ten.
member
Activity: 94
Merit: 10
Um, is it just my imagination, or is Groestl finding a boatload of blocks again today?

Check out http://birdonwheels5.no-ip.org:3000/.
legendary
Activity: 1361
Merit: 1003
Don`t panic! Organize!
My qubit node updated  http://p2pool-eu.gotgeeks.com:5567

But still experiencing
Code:
 Worker gpu submitted share with hash > target:
in log on qubit.
Anyone managed to get rid of it w/o removing it from code? ;]


edit:
1st block http://myr.theblockexplorer.com:2750/block/222b928dfbbf1bcfc8c4281a42cf98b518a9cf4cd050bed0a616946e463b6c7c Cheesy
legendary
Activity: 1361
Merit: 1003
Don`t panic! Organize!
Looks like I finally manage to make ONE P2Pool code for all Myriad coins!
I have to reset share chains because:
- some algos are on old P2Pool code (old share chain data)
- I changed EVERY chain data

Major changes:
- all PPLNS window is 12hrs in every algo
- fast pool share reaction on miners come/leave (10-20 shares)
- scrypt and sha algo have longer share time to work on almost all scrypt machines
- rest of algos have 10s share time

What is not changed:
- P2P and miners ports

I will try to run all pools on my machine tomorrow, but it need to run 5 instances of myriadcoind and 5 copies of data directory, not sure that my machine handle it Tongue

Code: https://github.com/Rav3nPL/p2pool-myriadcoin

Because all chains have "persist" flag set to "true" 1st pool owners need to change it ofc Smiley
I have checked on testnet SHA, qubit and skein for proper block - it works fine. But I not see how 2 others would not work Smiley
sr. member
Activity: 448
Merit: 250
The Time-Warp Attack Revisited: Questions

A) When did it start happening and can we see this on an explorer?

B) It did not fork Myriadcoin yet time-warp attacks have forked other mono-PoW coins in the past. Do we have cited occasions for this?

C) Can someone do a write-up of how Myriadcoin successfully survived the time-warp attack and how our multi-PoW mechanism minimized the damage? I think this is a tremendous selling point.

D) Can time-warp attacks still be performed? If they can, can we prove on the blockchain when they may have occurred and point to specific changes in the source code that prevented it from doing as much damage as it did this past weekend?

E) Now that the difficulty-weighting adjustments, 6-block consecutive mining cap per algo, and the time-warp failsafes have been integrated, what kind of confidence should this give investors and devs in using/buying Myriadcoin? Is the blockchain woven better than Bitcoin's?
sr. member
Activity: 448
Merit: 250
7 blocks in a row? Not anymore, buddeh.

Groestl tried recently, only got 6. Lovin' it!
sr. member
Activity: 336
Merit: 250
Why no just update code that need be updated? Can`t even easy check changes you have made...
Yes sorry, i have copy paste the whole folder from my server and a backup file that should not be on the git make it hard to read.

Changes are in bold:
p2pool/networks.py:
Quote
myriadcoinqubit=math.Object(
PARENT=networks.nets['myriadcoinqubit'],
SHARE_PERIOD=10, # seconds
NEW_SHARE_PERIOD=10, # seconds
CHAIN_LENGTH=24*60*60//10, # shares
REAL_CHAIN_LENGTH=24*60*60//10, # shares
TARGET_LOOKBEHIND=50, # shares //with that the pools share diff is adjusting faster, important if huge hashing power comes to the pool
SPREAD=30, # blocks
NEW_SPREAD=30, # blocks
IDENTIFIER='aa70135c700a00ee'.decode('hex'),
PREFIX='aa72ef181e88efcb'.decode('hex'),

P2P_PORT=5566,
MIN_TARGET=0,
MAX_TARGET=2**256//2**20 - 1,
PERSIST=False,
WORKER_PORT=5567,
BOOTSTRAP_ADDRS='p2poolcoin.com'.split(' '),
#ANNOUNCE_CHANNEL='#p2pool',
VERSION_CHECK=lambda v: v >= 90206,
),

p2pool/bitcoin/networks.py:
Quote
myriadcoinqubit=math.Object(
P2P_PREFIX='af4576ee'.decode('hex'),
P2P_PORT=10888,
ADDRESS_VERSION=50,
RPC_PORT=10889,
RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
'myriadcoinaddress' in (yield bitcoind.rpc_help()) and
not (yield bitcoind.rpc_getinfo())['testnet']
)),
SUBSIDY_FUNC=lambda height: 1000*2000000000000 >> (height + 1)//967680,
BLOCKHASH_FUNC=lambda data: pack.IntType(256).unpack(__import__('qubit_hash').getPoWHash(data)),
POW_FUNC=lambda data: pack.IntType(256).unpack(__import__('qubit_hash').getPoWHash(data)),
BLOCK_PERIOD=30, # s
SYMBOL='MYR',
CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'Myriadcoin') if platform.system() == 'Windows' else os.path.expanuser('~/Library/Application Support/Myriadcoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.myriadcoin'), 'myriadcoin.conf'),
BLOCK_EXPLORER_URL_PREFIX='http://explorerino.com/block/',
ADDRESS_EXPLORER_URL_PREFIX='http://explorerino.com/address/',
TX_EXPLORER_URL_PREFIX='http://explorerino.com/tx/',
### Neisklar: normally 2**24 should be 2**20 BUT the quark enabled minerd is coded so that it only detects hashes below 0x000000xxxxxxx
### and 2*20 would be 0x00000FFFF, maybe changing that in the miner would be a good idea for slower ones...
### Update: the minerd is (at least in GitHub) updated so that it would also detect targets below 2**24 (0x000000xxxx..), (Quark$
### maybe for new standalone p2pools it's a good choice at the beginning, but ONLY when new hashing power is gradually a$
#SANE_TARGET_RANGE=(2**256//2**32//1000 - 1, 2**256//2**24 - 1),
SANE_TARGET_RANGE=(2**256//2**32//1000 - 1, 2**256//2**20 - 1),
DUMB_SCRYPT_DIFF=1,
DUST_THRESHOLD=0.001e8,
),


p2pool/bitcoin/p2p.py:
Quote
def connectionMade(self):
self.send_version(
version=70002,
services=1,


Jump to: