Somewhere in Suginami, Tokyo
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/sh | |
# Check to see if the directory exists | |
if [ ! -d $HOME/.ftb ] | |
then | |
mkdir $HOME/.ftb | |
fi | |
# Check to make sure the launcher is in the directory | |
if [ ! -f $HOME/.ftb/FTB_Launcher.jar ] |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
# Just print out the secrets file as-is if the password file doesn't exist | |
if [ ! -r '.vault_password' ]; then | |
cat | |
exit | |
fi | |
CONTENT="$(cat)" | |
# Store vault's stderr in RESULT and redirect encrypted stdout back to stdout | |
{ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[center][img]http://i.imgur.com/HcUPhE3.png[/img] | |
[size=15pt]http://monacoin.org/en/[/size] | |
[b][color=blue][size=15pt]Specifications[/size][/color][/b] | |
Algorithm: Lyra2REv2 (originally Scrypt until block 450000) | |
Premine: none | |
Block reward: 50 MONA | |
Block time: 1.5 minutes | |
Retarget: 1 block (Dark Gravity Wave algorithm, hard fork at block 450000) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MonacoinprojectはASICを否定しません。 | |
ASICは消費電力、ネットハッシュの確保(=攻撃コストの増加)という点で有効です。 | |
(同じようなことを2014年にもどこかで書いた記憶が・・・) | |
先のアルゴリズム変更は遅延を解消することが目的で、"結果的"にscrypt-ASICが使えなくなったという事です。 | |
もっとも当時のscryptはSHA256に次ぐ採用率の高いアルゴリズムであったので、他のコインへの流用は十分可能だったと思います。 | |
将来的にLyra2REv2でも遅延・寡占が問題になった場合はアルゴリズムの変更が検討されるでしょう。 | |
ASICの首を絞めるのはASICによって遅延を引き起こす一部のユーザーにあります。 | |
逆に遅延も無く、高いネットハッシュが安定して続くのであればアルゴリズムの変更はありません。 |