We offer a wallet deployment service for coins, with features for new and established coins alike. Save development time and bureau-"crazy". Become listed on a multicurrency wallet. Offer your users an easy to use platform for investing.

The Web, Android and iOS wallets work on the same gateway - Once registered, users can access the same wallet from all platforms and perform the same actions.

Apart from the white label wallets, you can benefit from optional advantages:

- Implementation of your coin into a multicurrency wallet
- Shared masternode service built into the wallet, with instant rewards for investors. No VPN, no masternode setup required
- Let your investors buy your coin directly with Fiat (available in Q4 2018)
- Instant coin exchanges between cryptocurrencies in the multicurrency wallet (available in 2019)

More about the service can be found in the official presentation: Wallet AiO Presentation

You can contact us at sales@megano.co, ask in our Trittium Discord Channel or send me a PM. Feel free to post questions and feedback

Thanks for the answers, appreciate it. The ease of use is certainly a good point.

So, you are basically hedging, and, if i am not mistaken you leverage the time delay between the dollar adjustment between BTC /coins with USD trading pairs and alts or both. That would be indeed nice and an advancement in the exchange environment.

Haven't "read" the whitepaper, only scanned before the last post cause I didn't see answers to my concerns. But. X11 is a good choice for qcore, although I am still somewhat concerned about a confirmation time of approx. 40 minutes according to confirmation amount and block time. Have you planned / talked to exchanges to cooperate on this? If the exchange was instant, you would have a huge advantage over the classic bots.

Interesting project, but I do not see the point in making an ICO (yet).

What is the difference to free and open source software like CCXT?

There are many good bots around and trading platforms for strategies, what leverage do you have over them?

Is your algorithm solely about arbitrage, does it contain proven strategies like MACD or do you have a different approach?

If you use a mineable qcore coin for establishing trade between different exchanges, what about confirmation time vs chain security and is a mineable coin not a limitation to your product?

Good luck

From what I've read in the thread and telegram, minex and the implemented algo are interesting and I really like the ideas of Minexcoin and -Bank. However, 1) 5% a day is still quite big for a coin which aims to be somewhat a stable coin, 2) being an algo and interfering (only in emergency cases) in the markets - it sounds to me like a bet on human rationality, which is... well... you know. 3) Aiming for stability towards fiat instead of btc or the crypto top 10 in times when investments in crypto get somewhat shuffled, I personally see the possibility of huge fluctuations, it will be at least interesting to see how the price develops with that and your algo adjusts to it, keeping the 5% in mind. Apart from that, thumbs up for your progress so far. Permanent development, constant progress on the roadmap, I like the Minexbank app and lately lightning transactions with btc and ltc (which I very much miss just the mention of it from newer coins), I am looking forward to hear more and keep parking a few mnx. I would like to hear more about your plans for Q3 and Q4 especially for mining, but that is still 'far' away, so keep up the good work 

https://stipend.me/devs-weekly-update-005/

There you go

So I am checking the fixed version now. Speed is a bit better than before, but still about 20% less than v0.13. It appears to be related to the CPU, any change to the CPU affinity in the task manager heavily affects the hashrate. Still, I did not have the problem with v0.13. I'll be sticking with the new version for now and see what it can do over time.

btw. Any chance to include a logfile, to see hashrates and how often the miner had to restart?

Thanks, that is awesome!

Worked like charm. For 5 seconds. Then the pool went down.

Will report more once I can run it again. Is it possible to combine the "set sleep duration" with the v0.13 thread model?

v0.13, my bad.

this is my current batch, I've tried "WORKB" with 1,2,3,4,5,8,12, all max -20% of v0.13. Also tried using the v0.21 for one card, same result. This batch is from the last test on one card:

Rem Insert your pool name here
set "POOL=mnx.suprnova.cc"               
Rem Insert your pool port here
set "PORT=7077"
Rem Insert your user and worker names here                  
set "USER=xxxxx"     
Rem Insert your worker password here
set "PASS=xxxxxx"   

Rem Insert the index of the platform you want to run on. Run lolMiner-mnx.exe --list-devices
Rem to see all available platforms and the available devices for each platform
set "PLATFORM=1"   
Rem Insert your devices to run the miner here. For multiple GPU pass a comma separated list, e.g.: 0,1 for using two GPUs             
set "DEVICE=0"
Rem Set the work-batch-size (see readme file)
set "WORKB=3"

The batch for the v0.13 is this:

lolMiner-mnx.exe --server mnx.suprnova.cc --port 7077 --user xxxxx -- pass xxxxx --platform 1 --enable-nv-hotfix

works fine on 18khash per card apart from the occasional shutdowns of the miner.

edit: I don't think it is related, but my onboard graphics (intel) is platform 0 and is used as primary. MB is 110 Pro BTC+

Hi, I was using v0.15 with two GTX 1080 TI and then tried to switch to v0.20 and v0.21. I played with the batch a little but I never got more than 80% of the hashrate of the v0.15. Hope this gets better (again). Good work so far 

Hi tutulfo, short question. Going through the Include.ps1, I wonder if it is possible to set the max power limit of the GPU to a fixed number, not a percentage?

So for example, 150w for one card instead of 80%. This would be very useful, but I am not sure if that is something possible to do by software.

Keep up the good work 

Good joke. You guys realize that Bitmain sells GPU rigs? They wouldn't have started selling GPU rigs if they had an ETH asic in the pipeline and release it 6 months later, not to speak of the numbers not adding up.

Glad to hear a new release is on its way. I am having trouble with the DB, it takes hours to rebuild. Last time, the daemon lasted just about an hour after rebuilding the DB on one machine. Though the other machine ran +24h without issues.

If it is technically feasible at the moment, I suggest a miner build into a wallet, it has some advantages. I think it would also best suit your reward structure (1.9+1) and spread the hashrate, especially if you add mobile wallets. The wallet/miner from coinage looks promising although they are in a very early stage, too.

Today I got issues with the coindesk api. MM could not receive it. Opened the address in my browser, it worked. So I set the timeout in core.ps1 to 5 seconds and it also worked in MM.

Suggestion for a failsave: Would it be possible to save the last api locally and call the local file if the api is not available online? Or, as an alternative, save the output from the coindesk api in the log file and use last stats from the logs if the api is unavailable?

600% p.a., not a day 

I remember them saying that they change the algo once they release mining publicly. Targeted block time was supposed to be 1 minute. Hasn't happened (yet), hopefully it is still planned to do so. Maybe they just needed some hashpower to speed up transactions. Scrypt really sucks, centralized ASIC mining with high block time.

I had that problem when experimenting with OC. Had it again when I got another card of the same brand and applied the sync function in AB.

The problem is very likely not related to any mining software but your OC or the cards drivers, from my experience. Did you alter the clock curve in the OC-software? Driver failure at miner shutdown usually appears when the voltage of your card drops and the lower voltage can not handle the load.

Is there still a plan to change to another algorithm?

Hey tutulfo, first, thanks for the great miner and your developing.

I am having the same issues as celofan in 2. and 3., a new interval just starts too early. i have set benchmark and mining interval both to 600 in the config, but the new interval always starts after 1-3 minutes.

i did not have the issue in previous releases, so my guess is that a new or changed parameter is overriding the interval time from the config time.

another observation is that currently i am mining on 2 pools. one api is not responding, pool issue. but since the api is not responding, MM restarts the interval every few seconds. almost like an instant override of the interval time from the config

One 8-pin power connector and cable of the PSU should be able to handle 2 connections to the GPU. however, running 3 cards with 2x8 pin connectors, you should check the power draw of the cards. could be too much for one 750w psu if you also connect the mb, cpu, hdd and risers to it. you can also check the splitters by adding them one by one and let it run for some time. another point: do you start your 2nd psu manually or do you have a psu adapter for it? add2psu adapter could be one cause, too