Topic: [ANN] [POW] [MSR] Masari - simple, scalable, and secure cryptocurrency - page 50. (Read 85421 times)

Right, with the new rule on CMC to list only coins with daily 100k volume, Aeon and Sumo would not have been listed (if they were new coins) because they have about 30k daily trades. That seems pretty unfair considering that are hundred of coins already listed on coinmarketcap.com with 0$ MarketCap.

New exchanges could come eventually with time (remember that MSR had no ICO like tokens can do, neither a premine that could pay for listing in good and big exchanges), as like the CMC listing (their new rule to list only coins with daily 100k volume will difficult all the new mineable coins to get listed early on it).

I think this currency will worth something in the future. The current goal for Masari should be listing on coinmarketcap.com and other exchanges.

Masari seems ready to change PoW against the ASICs, well done! https://github.com/masari-project/masari/pull/9

Last weeks price is going up, in contrast to the majority of other alts. That's nice.

Masari now also has a cold paper wallet for anyone that is interested.

https://www.getmasari.org/masari-wallet-generator.html

The Vicex exchange banned us for "cheating" after we surfaced concerns about a security flaw in their database (plain-text passwords).

The Masari community is in agreement to avoid this one, and I recommend anybody who has made an account there with a reused password to immediately change their password where needed.

Sup Bro,
If your using my video, i just wanna make sure you have checked a few things.  When I ran into issue with sending payments, it was the masari-wallet-rpc application which wasn't set up correctly.  I have it right in the video [after messing up and redoing it in the video] but all was working well.  If the problem is prior to the automatic payouts, check out my config.json file to double check.  Also please don't hesitate to delete your config.json and create new from the config_example.json file - incase a comma or something small is missing.  and double check your wallet address.  If not, maybe a dependancy is missing, so start with a new OS installation and try again.  It took me about 15 'start-overs' before i got it working stable.

What I recommend [if the issue is somewhere in the config.json file is to remove and recreate it.

$ cd pool/
pool$ ls
config_example.json config.json init.js lib LICENSE logs node_modules package.json README.md redisBlocksUpgrade.js website_example
pool$ rm -r config.json
pool$ cp config_example.json config.json
pool$ sudo nano config.json

//items changed are in bold - dont be lazy and cut and paste, look for the values and change them manually.

{
    "coin": "masari",
    "symbol": "MSR",

    "logging": {
        "files": {
            "level": "info",
            "directory": "logs",
            "flushInterval": 5
        },
        "console": {
            "level": "info",
            "colors": true
        }
    },

    "poolServer": {
        "enabled": true,
        "clusterForks": "auto",
        "poolAddress": "5oKFSDn6vcEM89cgJ3EJw7Vb5PVmVNTE8EAVT5TJsCYFLotmkgxyrsDMwFCwqMtsYuDD4ECmbbDbCJC mbLi9suw1NXqArfu",
        "blockRefreshInterval": 1000,
        "minerTimeout": 900,
        "ports": [
            {
                "port": 3333,
                "difficulty": 1000,
                "desc": "CPU Mining Port"
            },
            {
                "port": 5555,
                "difficulty": 5000,
                "desc": "GPU Mining Port"
            },
            {
                "port": 7777,
                "difficulty": 400500,
                "desc": "NiceHash Mining Port"
            },
            {
                "port": 8881,
                "difficulty": 400500,
                "desc": "Hidden",
                "hidden": true
            }
        ],
        "varDiff": {
            "minDiff": 2,
            "maxDiff": 600000,
            "targetTime": 100,
            "retargetTime": 30,
            "variancePercent": 30,
            "maxJump": 100
        },
        "shareTrust": {
            "enabled": true,
            "min": 10,
            "stepDown": 3,
            "threshold": 10,
            "penalty": 30
        },
        "banning": {
            "enabled": true,
            "time": 600,
            "invalidPercent": 25,
            "checkThreshold": 30
        },
        "slushMining": {
            "enabled": false,
            "weight": 300,
            "blockTime": 60,
            "lastBlockCheckRate": 1
        }
    },

    "payments": {
        "enabled": true,
        "interval": 600,
        "maxAddresses": 50,
        "mixin": 12,
        "transferFee": 5000000000,
        "minPayment": 1000000000000,
        "denomination": 1000000000000
    },

    "blockUnlocker": {
        "enabled": true,
        "interval": 30,
        "depth": 60,
        "poolFee": 0.0,
        "devDonation": 0.0,
        "coreDevDonation": 0.0
    },

    "api": {
        "enabled": true,
        "hashrateWindow": 600,
        "updateInterval": 5,
        "port": 8117,
        "blocks": 30,
        "payments": 30,
        "password": "test"
    },

    "daemon": {
        "host": "127.0.0.1",
        "port": 38081
    },

    "wallet": {
        "host": "127.0.0.1",
        "port": 38082
    },

    "redis": {
        "host": "127.0.0.1",
        "port": 6379,
        "auth": null
    }
}

CTRL+X
Overwrite Changes? 'Y' then [Enter]

Tell me if you have any luck

Masari is doing it right. It is honest and open. Pay attention to it we shall.

The Transfer Fee is how much you must charge per payment to a user's wallet.  The Transfer isn't free.  On my pool, I created 0% Fees across the board, and 0.005 MSR per transfer of funds.  I like it because its a static number which makes it simple to understand.  I am currently breaking even [Pool Profits are Profit 0.000000000042 MSR] which is where I want to be for now.  I plan to Increase fees to ward off miners when the pool's hash becomes 15-25% of the total hashing power of the network.  You should be responsible as a pool operator, and do what is best for the coin, even if it cuts into your pocket.  The long term rewards will be greater.

Take a look at my pool to see an example: http://Masari.CryptoNight-Mining-Pool.com

I agree. From all the other Monero forks, i think Masari might be one to actually pay attention to.

Did you click connect? There is a button for it. It works for other users. Come ask more detailed questions in the Discord. @Girugamesh in the Discord could probably help troubleshoot more than I. Here is the link https://discord.gg/sMCwMqs

I'll repeat, why it does not work connect remote daemon in gui-wallet?
Settings - Daemon address and port - no connection

What are the next plan for this project ?

Thanks...will try that...

I would get on Masari'sReddit page and ask the guy who made the pool video. I see him on their quite a bit. Goodluck

I already had the exact same settings for the payments section but payments don't go thru:

    "payments": {
        "enabled": true,
        "interval": 600,
        "maxAddresses": 50,
        "mixin": 12,
        "transferFee": 50000000000,
        "minPayment": 10000000000000,
        "denomination": 1000000000000
    },

Log simply says failed payment. Any ideas?

Thanks!

You can use this video for configure your pool. It's great for masari 

https://www.youtube.com/playlist?list=PLHNd4pjwyMCUi2wJHrhoV7unhvgKcwOYX

Hi guys. We published a new pool for Masari  Fee is just 0.5 %, we are going to moon   
Pool url : http://www.msrpool.ir
We gonna give gifts as Masari

Could anyone please let me know what settings we need for the payment section of the node-cryptonode-pool (for Masari)?
I am not clear what value to use for transferFee?!

Cheers!