 Show Posts
|
|
Pages: [1] 2 »
|
Ich möchte keine Details nennen weil ich mich vor Schadensersatzklagen der Betreiber schützen möchte.
Wenn ich hier irgendetwas behaupte das ich im Klagefall nicht zu 100% beweisen kann verliere ich nämlich noch mehr Geld - und darauf kann ich verzichten.
Sehr vorausschauend. Recht hast du natürlich. Demnach scheinst du also zumindest beweisen zu können, dass anycoin unseriös und unkooperativ ist. Das ist doch schonmal was, auch wenn uns der Beweis nicht zugänglich ist. Da du allerdings im anderen Thread meintest, dass du einiges an Geld verloren hättest, stellt sich mir eher die Frage, ob du das Rechtlich verfolgst bzw. ob du das bereits getan hast. Da ich in deutschland sitze und anycoindirect in den Niederlanden ist eine Strafverfolgung nur sehr schwer möglich - zudem gelten die Niederländischen Gesetze die ich leider nicht gut genug kenne. Ich kann den Ausfall verschmerzen und möchte einfach nur meine Erfahrungen teilen, damit nicht noch weitere Leute in die Falle tappen. Von Strafverfolgung war auch eher weniger die Rede  Aber gut, wenn du meinst, dass es sich nicht lohnt, dann ist das so. Je nach Betrag kann es meiner Meinung nach allerdings nicht schaden sich eine erste Meinung von einem Anwalt zu holen. Wie gesagt, ich weiß nicht um wieviel es geht, aber so ne erste Meinung kostet meist nicht mehr als 200€, womit es sich meiner Meinung nach schon bei einem sehr gerinfen vierstelligen betrag lohnen würde. Aber gut, wenn du damit abgeschlossen hast und dennoch gut schlafen kannst, dann hast du so wenigstens deine Ruhe. Kann natürlich auch von Vorteil sein. Als deutscher Kunde, kannst du mit deutschem Gerichtsstand klagen, dann gilt deutsches Recht. Darüber hinaus kannst du im Land der Ansässigkeit des Unternehmens Klagen, sowie in jedem Anderem Land auf dessen Recht auch nur teile der AGB beruhen. Bsp.: In den AGB befinden sich Punkte die nach Irischen, oder Französischen Recht verfasst sind, so ist dies zulässig, wenn ausdrücklich genannt wird dass in den AGB Punkte nach dem Recht der jeweiligen Länder verfasst sind. Klagt der Kunde nun in Frankreich, werden die gesamten AGB, nicht nur der nach französischem Recht verfasste Punkt, nach französischem Recht verhandelt. Fakt ist, es gelten mit nichten Niederländische Gesetze. |
|
|
|
Having some sync issues with the wallet. I tried already to purge the data folder for a full resync but now I am stuck at block 0.
I have put the below to my conf.
connect=104.128.225.215
connect=104.128.225.240
connect=104.128.225.241
connect=104.131.42.100
connect=216.189.144.186
connect=216.189.144.211
connect=216.189.144.212
connect=104.131.42.100
connect=xmg.suprnova.cc
What exactly do you mean with "I tried already to purge the data folder", you need to close the Wallet and delete "blocks" "database" "peers.dat" NOT wallet.dat go to your config and put addnode=104.128.225.215
addnode=104.128.225.240
addnode=104.128.225.241
addnode=104.131.42.100
addnode=216.189.144.186
addnode=216.189.144.211
addnode=216.189.144.212
addnode=104.131.42.100
addnode=xmg.suprnova.cc into it, save exit. Go to http://coinmagi.org/bin/block-chain download m-block-chain.zip and unzip "blocks" and "database" into your wallet folder. Start wallet, now it should recync the last few blocks. |
|
|
|
[SNIP]
I can upload the debuglog for you if you need.
I had a similar problem before and a full reload of the blockchain with the good nodes in my magi.conf helped me. Doesnt help the Wallet cant get across block 1217757, curious is that only 1 Wallet is affected all others run fine. trying connection [2a02:8108:8b40:d18:7c2b:c1cd:eab:179c]:8233 lastseen=211.4hrs
Added 618 addresses from 104.207.149.217: 9 tried, 9591 new
Added 659 addresses from 104.207.149.217: 9 tried, 9562 new
Added 334 addresses from 104.207.149.217: 9 tried, 9568 new
connection timeout
connection timeout
trying connection 87.78.184.144:8233 lastseen=66.4hrs
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection 97.102.77.41:8233 lastseen=5.1hrs
connection timeout
trying connection 190.142.243.32:8233 lastseen=156.6hrs
received block d6cf05d12962e8050414
ProcessBlock: ORPHAN BLOCK, prev=000000001a3ae11324ab
received block 000000001a3ae11324ab
ProcessBlock: ORPHAN BLOCK, prev=000000002ab5124acfec
received block 000000002ab5124acfec
ProcessBlock: ORPHAN BLOCK, prev=4ecb39f3529c09caee2e
received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout
trying connection 2.236.133.147:8233 lastseen=89.7hrs
connection timeout
trying connection 84.215.7.210:8233 lastseen=1.1hrs
Flushed 9577 addresses to peers.dat 61ms
connection timeout
trying connection 46.188.1.45:8233 lastseen=1.1hrs
connection timeout
trying connection 37.214.136.230:8233 lastseen=44.6hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
socket no message in first 60 seconds, 0 1
disconnecting node 104.131.42.100:8233
connection timeout
trying connection 37.47.104.190:8233 lastseen=673.3hrs
connection timeout
trying connection 87.212.198.241:8233 lastseen=1.1hrs
connection timeout
trying connection 187.78.19.191:8233 lastseen=67.9hrs
connection timeout
trying connection 188.66.69.56:8233 lastseen=1.1hrs
connection timeout
trying connection 220.214.11.117:8233 lastseen=121.0hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
received block 0dcaf99ecad91eb3f70b
ProcessBlock: ORPHAN BLOCK, prev=d6cf05d12962e8050414
connection timeout
trying connection 95.42.179.205:8233 lastseen=1.1hrs
connection timeout
trying connection [2601:196:8901:898a:51c1:337c:5f7d:68fa]:8233 lastseen=177.7hrs
connection timeout
trying connection 89.204.155.43:8233 lastseen=890.8hrs
connection timeout
trying connection 154.119.225.5:8233 lastseen=1.1hrs
connection timeout
trying connection 96.248.122.64:8233 lastseen=6.2hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection [2a06:8ec0:3::1:28e6]:8233 lastseen=2.3hrs
connected [2a06:8ec0:3::1:28e6]:8233
send version message: version 71051, blocks=1217757, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:8233, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
Added time data, samples 9, offset -22 (+0 minutes)
nTimeOffset = -23 (+0 minutes)
Moving [2a06:8ec0:3::1:28e6]:8233 to tried
receive version message: version 71051, blocks=1219032, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:50836, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
trying connection 104.251.215.107:8233 lastseen=0.3hrs
connected 104.251.215.107:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.251.215.107:8233, peer=104.251.215.107:8233
received block 0000000003025a87a9cc
ProcessBlock: ORPHAN BLOCK, prev=0dcaf99ecad91eb3f70b
trying connection 46.188.1.45:8233 lastseen=1.1hrs
trying connection 104.128.225.215:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
Added 619 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9764 new
received block 0000000017106db73b6d
ProcessBlock: ORPHAN BLOCK, prev=0000000003025a87a9cc
Added 639 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9894 new
connection timeout
Added 332 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9940 new
trying connection 104.128.225.240:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
connection timeout
trying connection 104.128.225.241:8233 lastseen=385654.5hrs
Added time data, samples 10, offset -24 (+0 minutes)
receive version message: version 71041, blocks=1219033, us=87.157.60.239:63622, them=104.251.215.107:8233, peer=104.251.215.107:8233
Flushed 9950 addresses to peers.dat 46ms
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 104.131.42.100:8233 lastseen=385654.5hrs
connected 104.131.42.100:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.131.42.100:8233, peer=104.131.42.100:8233
trying connection 178.33.228.14:8233 lastseen=385654.5hrs
received block 0000000027ba1ac55030
Misbehaving: 110.11.227.163:8233 (0 -> 100) DISCONNECTING
disconnecting node 110.11.227.163:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout I can upload the debuglog for you if you need. I suppose you already tried restarting the wallet. Firstly, see if block 1217757 is on the right chain. A quick verification is to check its hash daemon: magid getblockhash 1217757 qt-wallet under console: 819506440fe4287e605022bac64465b36a26d9fc2e0c5d9423f0fe63428a3960 should be the output. Some details of this block: https://chainz.cryptoid.info/xmg/block.dws?819506440fe4287e605022bac64465b36a26d9fc2e0c5d9423f0fe63428a3960.htmOnce this is confirmed, put the following in magi.conf to force connecting with these nodes only (no addnode), then restart wallet: connect=104.128.225.215
connect=104.128.225.240
connect=104.128.225.241
connect=104.131.42.100
connect=216.189.144.186
connect=216.189.144.211
connect=216.189.144.212
connect=104.131.42.100
connect=xmg.suprnova.cc If the above doesn't help, we might consider resync the blockchain; use the block data here: http://coinmagi.org/bin/block-chain. If you can upload the debug.log, I can double check. Thank you for your quick answers! Unfortunately i already followed starmman and did the resync. But maybe this will help others with the same problem, also it would be interesting to know how this happened. |
|
|
|
I'm running the new wallet but I see this error and can't get past the block...
received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
received block 0000000027ba1ac55030
Misbehaving: 104.222.96.36:8233 (0 -> 100) DISCONNECTING
disconnecting node 104.222.96.36:8233
ERROR: ProcessBlock() : block with too little proof-of-work
Also got those issues, always losing connection. It seems due to connection with misbehaved peers, which are supposed to be disconnected. Pls try to remove peers.dat, add only the following nodes, and restart the wallet: addnode=104.128.225.215
addnode=104.128.225.240
addnode=104.128.225.241
addnode=104.131.42.100
addnode=216.189.144.186
addnode=216.189.144.211
addnode=216.189.144.212
addnode=104.131.42.100
addnode=xmg.suprnova.cc Doesnt help the Wallet cant get across block 1217757, curious is that only 1 Wallet is affected all others run fine. trying connection [2a02:8108:8b40:d18:7c2b:c1cd:eab:179c]:8233 lastseen=211.4hrs
Added 618 addresses from 104.207.149.217: 9 tried, 9591 new
Added 659 addresses from 104.207.149.217: 9 tried, 9562 new
Added 334 addresses from 104.207.149.217: 9 tried, 9568 new
connection timeout
connection timeout
trying connection 87.78.184.144:8233 lastseen=66.4hrs
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection 97.102.77.41:8233 lastseen=5.1hrs
connection timeout
trying connection 190.142.243.32:8233 lastseen=156.6hrs
received block d6cf05d12962e8050414
ProcessBlock: ORPHAN BLOCK, prev=000000001a3ae11324ab
received block 000000001a3ae11324ab
ProcessBlock: ORPHAN BLOCK, prev=000000002ab5124acfec
received block 000000002ab5124acfec
ProcessBlock: ORPHAN BLOCK, prev=4ecb39f3529c09caee2e
received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout
trying connection 2.236.133.147:8233 lastseen=89.7hrs
connection timeout
trying connection 84.215.7.210:8233 lastseen=1.1hrs
Flushed 9577 addresses to peers.dat 61ms
connection timeout
trying connection 46.188.1.45:8233 lastseen=1.1hrs
connection timeout
trying connection 37.214.136.230:8233 lastseen=44.6hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
socket no message in first 60 seconds, 0 1
disconnecting node 104.131.42.100:8233
connection timeout
trying connection 37.47.104.190:8233 lastseen=673.3hrs
connection timeout
trying connection 87.212.198.241:8233 lastseen=1.1hrs
connection timeout
trying connection 187.78.19.191:8233 lastseen=67.9hrs
connection timeout
trying connection 188.66.69.56:8233 lastseen=1.1hrs
connection timeout
trying connection 220.214.11.117:8233 lastseen=121.0hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
received block 0dcaf99ecad91eb3f70b
ProcessBlock: ORPHAN BLOCK, prev=d6cf05d12962e8050414
connection timeout
trying connection 95.42.179.205:8233 lastseen=1.1hrs
connection timeout
trying connection [2601:196:8901:898a:51c1:337c:5f7d:68fa]:8233 lastseen=177.7hrs
connection timeout
trying connection 89.204.155.43:8233 lastseen=890.8hrs
connection timeout
trying connection 154.119.225.5:8233 lastseen=1.1hrs
connection timeout
trying connection 96.248.122.64:8233 lastseen=6.2hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection [2a06:8ec0:3::1:28e6]:8233 lastseen=2.3hrs
connected [2a06:8ec0:3::1:28e6]:8233
send version message: version 71051, blocks=1217757, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:8233, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
Added time data, samples 9, offset -22 (+0 minutes)
nTimeOffset = -23 (+0 minutes)
Moving [2a06:8ec0:3::1:28e6]:8233 to tried
receive version message: version 71051, blocks=1219032, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:50836, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
trying connection 104.251.215.107:8233 lastseen=0.3hrs
connected 104.251.215.107:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.251.215.107:8233, peer=104.251.215.107:8233
received block 0000000003025a87a9cc
ProcessBlock: ORPHAN BLOCK, prev=0dcaf99ecad91eb3f70b
trying connection 46.188.1.45:8233 lastseen=1.1hrs
trying connection 104.128.225.215:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
Added 619 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9764 new
received block 0000000017106db73b6d
ProcessBlock: ORPHAN BLOCK, prev=0000000003025a87a9cc
Added 639 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9894 new
connection timeout
Added 332 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9940 new
trying connection 104.128.225.240:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
connection timeout
trying connection 104.128.225.241:8233 lastseen=385654.5hrs
Added time data, samples 10, offset -24 (+0 minutes)
receive version message: version 71041, blocks=1219033, us=87.157.60.239:63622, them=104.251.215.107:8233, peer=104.251.215.107:8233
Flushed 9950 addresses to peers.dat 46ms
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 104.131.42.100:8233 lastseen=385654.5hrs
connected 104.131.42.100:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.131.42.100:8233, peer=104.131.42.100:8233
trying connection 178.33.228.14:8233 lastseen=385654.5hrs
received block 0000000027ba1ac55030
Misbehaving: 110.11.227.163:8233 (0 -> 100) DISCONNECTING
disconnecting node 110.11.227.163:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout I can upload the debuglog for you if you need. |
|
|
|
I'm running the new wallet but I see this error and can't get past the block...
received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
received block 0000000027ba1ac55030
Misbehaving: 104.222.96.36:8233 (0 -> 100) DISCONNECTING
disconnecting node 104.222.96.36:8233
ERROR: ProcessBlock() : block with too little proof-of-work
Also got those issues, always losing connection. |
|
|
|
Looks like BTC has hit its all time high - Magi still seems to be holding up pretty well compared to most other coins. Price vs BTC has dropped but we havn't lost the recent rise in market cap.
Yes Magi is doing very nice. Btc might drop little more next week. I hope so - the BTC bull has been stronger than I expected again. Looks like its going up again! Market cap value is looking very good - we are stabilising at around the 200k mark, if it stays where it is for a bit longer I think there is a good chance for a further rise. I agree with that. We will continue with the awesome future of Magi. as soon as joe update POW diff engine + dynamic diff based reduced rewards we will see much less POW coins rolled out per day and a way more competive coin inflation mining diff will increase with coin price and more miners joining and this way XMG have a automated selfmade POW reward reduction but yes the downside will be much of the time people mine for little gains but thats the idea of XMG POW that by reduce rewards with increasing diff u keep away the mining farms and single CPU who run 24/7 without care about diff and rewards will be the people who really earn the XMG POW coin rollout the sell pressure will be lot less and trader instead of miner will have main marketprice impact I like the idea behind new POW engine. It will be very interesting to see how it will influence the price of the coin and of course how interesting it will remain for ppl to mine it. Sure there will always be those who mine the coin cause they beleive in it. but those who mine it currently for profit, they could leave the coin as it will not be worth anymore.
This is verry hard to tune because if you lower the rewards to much you end up with only enthusiasts and botnets mining that dont care about electricity cost. To make sure to get always a fair reward the network has not only to scale considering the actual coin price, it also has to consider how many hashrate it needs at the moment accordingt to the amount of incoming transactions to always allow them to proced fast. To do this in perfection the network has to learn and predict a large arise before it occurs to make sure the hashrate is pumped when it hapens. To make it realy fair it also has to cut the reward of big pooled hashrate first, without touching the diff or reward of small contributers what is probably almost impossible. Just take a look on BTC transactions, the network is huge but sometimes transactions take a ridiculous long time while still charging a big transaction fee per kb. To use magi as a payment method as a customer that only wants to pay for goods i would presuppose that my transaction is almost instant like it is at the moment without taking care about how it is done. For sure it will take a lot time to get to the state where thousands of transactions per minute are done on the network but the goal should be to reach and handle this. Apart from this the best thing that could happen to a Crypto is a large comunity of solo miners with as less as posible big hashpower pools. |
|
|
|
yes no rewards and horrible weight. 2
It would be nice if you can provide a bit more informations like the ~amount of coins you have in the wallet in addition to your staking settings in your magi.conf like: posii=1
stakesplitthreshold=500
combinethreshold=250
While this sounds secondary, I'd post preliminary switch of logo to a new version (blue the primary) for clarity and simplicity:
  I propose in all of the situations where logos are used a switch should be done. Pls help to spread the words.
Here is a link to png files: http://coinmagi.org/files/logo/v2/, where you can also find the .svg. You're very welcome to improve / design logos.
@goldlabel, initial logo pngs will be remained here: http://coinmagi.org/files/logo/v1/ Give a hand on spreading the new logo if you can (I suppose it would be the favor of the most) (pool, exchange, etc). This would be sort of marketing and get us standing out. We'll follow up this change as well. Has our awesome Goldlabel did something with those already. If not pls Goldlabel could you take a look at these logo's. Will there be one in orange also? I like simplicity but maybe in 3D in would be better.  I realy like this simple Style for the wallet, but when it comes to web presence it can be a bit more flashy i in my opinion. I would like the new icon on a 3d coin like the old silver magi coin is. Like this BTC: https://img1.cgtrader.com/items/596931/d21abdcd1d/bitcoin-3d-model-max-3ds-fbx-c4d-ma-mb.jpg And maybe a larger one for headers where a lot of those 3d coins fall down in all 3 colours green blue orange. Like this one (of course in a better format for headers): http://static9.depositphotos.com/1006187/1130/i/450/depositphotos_11307591-stock-photo-rain.jpg |
|
|
|
I don't setting mint (staking) but why my wallet auto staking? how I fix it? thanks for reply
Do you use m-core:1.3.1 ? If yes you can klick on Mint -> Disable PoS Minting To turn auto PoS off klick Help -> Edit Magi.conf -> Strg F -> put posii=1 into the search line and set it to 0 in the config file. Save and exit, restart Wallet. To do it manual at Windows 10 navigate To: My Computer -> type C:\Users\[your windows username]\AppData\Roaming\Magi\magi.conf without [] Choose editor from the app list. Or just %appdata% navigate to magi and open magi.conf with editor. -> Strg F -> put posii=1 into the search line and set it to 0 in the config file. Save and exit, restart Wallet. If you set a passphrase and just have your wallet open without unlocking it, PoS is also disabled. But there is no reason to disable it in my opinion since it does not cause havy load on your system. Actually, I would say under normal usage there's no reason for it to be disabled. But if you run a service where you have transactions to and from that service. I would actually recommend it. But then we are talking about more special case. There is really good reason to have it set to off POSii=0 , if this is now hard coded in the new wallet XMG as posii=1 its just asking for forks, The chain must be fully synced before the wallet enters POS. Once a fork happens it is choas, exchanges lock down wallets, pools stop. Thinking I should look start looking different coins now if this is not addressed. Well i only can speak for myself but when i installed the new wallet i had to manual enable PoS after the first start and i still have to on every start, even with posii=1 in config. |
|
|
|
Maybe some one might need it, so i would like to share my solution to startup and hide miner in addition to startup and hide wallet for solo mining, it can also be used to autostart and hide miner while pool mining. I use this to reload everything after a windows update or restart for whatever reason. Also it hides the miner so it is only visible in the task manager because i dont want it in in my face, or getting accidently closed while doing other stuff on the device. (Do a test run with a normal start of the bat file before using the script to make sure everything is setup right in the miner itself.) To create the script we first need to show the file name extensions. On Windows 10 Start Windows Explorer, you can do this by opening up any folder. Click Organize. In the right top corner check show file name extensions. On Windows 7 Start Windows Explorer, you can do this by opening up any folder. Click Organize. Click Folder and search options. Click the View tab. Scroll down until you notice Hide extensions for known file types, un-check this line by clicking the check box. Now we Create [Yourfilename].txt Copy paste this in your .txt file and eddit the information related to your device without []. (rename the point \ run.bat to the name of the .bat you use to start your miner.) Set WshShell = CreateObject("WScript.Shell")
cmds=WshShell.RUN("C:\[the file path to your Minerd]\run.bat", 0, False)
Set WshShell = NothingSafe and exit. Now rename the file from [Yourfilename].txt to [Yourfilename].vbs Double klick and open the task Manager, check if your miner is runing with high cpu load. It it dies everything is fine. To put it into autostart press Windows Key+R and copy paste Copy [Yourfilename].vbs into the folder. Restart Device and check Task manager for miner process. For solo mining put a shortcut of m-wallet.exe into the autostart or simply check Start magi on system login in the wallet Configuration tab. You also can hide it into the info tab next to you clock by checking the Option in tue configuration. Kindly note that this only will work when your miner itself already is set up right. |
|
|
|
I don't setting mint (staking) but why my wallet auto staking? how I fix it? thanks for reply
Do you use m-core:1.3.1 ? If yes you can klick on Mint -> Disable PoS Minting To turn auto PoS off klick Help -> Edit Magi.conf -> Strg F -> put posii=1 into the search line and set it to 0 in the config file. Save and exit, restart Wallet. To do it manual at Windows 10 navigate To: My Computer -> type C:\Users\[your windows username]\AppData\Roaming\Magi\magi.conf without [] Choose editor from the app list. Or just %appdata% navigate to magi and open magi.conf with editor. -> Strg F -> put posii=1 into the search line and set it to 0 in the config file. Save and exit, restart Wallet. If you set a passphrase and just have your wallet open without unlocking it, PoS is also disabled. But there is no reason to disable it in my opinion since it does not cause havy load on your system. Actually, I would say under normal usage there's no reason for it to be disabled. But if you run a service where you have transactions to and from that service. I would actually recommend it. But then we are talking about more special case. Makes sense i have to admit that i didn't considered this. It for sure can be problematic when a big amount of coins is locked in stake if you have a lot of transactions in and especially out. |
|
|
|
I don't setting mint (staking) but why my wallet auto staking? how I fix it? thanks for reply
Do you use m-core:1.3.1 ? If yes you can klick on Mint -> Disable PoS Minting To turn auto PoS off klick Help -> Edit Magi.conf -> Strg F -> put posii=1 into the search line and set it to 0 in the config file. Save and exit, restart Wallet. To do it manual at Windows 10 navigate To: My Computer -> type C:\Users\[your windows username]\AppData\Roaming\Magi\magi.conf without [] Choose editor from the app list. Or just %appdata% navigate to magi and open magi.conf with editor. -> Strg F -> put posii=1 into the search line and set it to 0 in the config file. Save and exit, restart Wallet. If you set a passphrase and just have your wallet open without unlocking it, PoS is also disabled. But there is no reason to disable it in my opinion since it does not cause havy load on your system. |
|
|
|
Call me optimistic but I can't see why magi won't compete with the monero, dash, and eth of the world.
In my opinion it has to do a lot with the marketing machinery behind those projects, especialy Dash. But i look postive towards the future, since the new wallet has been released it seems like a lot of people that only followed the Forum are now active (me included) Also the network seems to get bigger pretty fast at the moment according to https://chainz.cryptoid.info/xmg/#!network and the actual average hashrate. |
|
|
|
Can anyone explain me or give me further information on how to solo mine with other devices on a different location to the same Wallet?
Do i need to instal the Wallet on every device and import my wallet.dat to do so or is there an other option to point devices directly to it?
Following the guide by Elar, https://bitcointalk.org/index.php?topic=735170.msg17899424#msg17899424; modify magi.conf to have the following (no square brackets): rpcallowip=[IP of your PC that will run miner] restart the wallet in order to reload magi.conf, then run the miner (no square brackets), ./m-minerd --url http://[IP of your PC that runs the wallet or magid]:8232 --user magi --pass 12345 --threads 4 -e 100 This should work.
*FACEPALM*
Im stupid...
Found the issue, fixed, now it is working well thank you!Would be good to know what your actual problem was and how you fixed it. In case someone else comes accross the same problem, he would only find "I fixed it" as solution which is absolutely unhelpful in any way. The exact soulution is what joelao95 posted, the problem was that i have interchanged some of the ips... Still Facepalm.  If you want to set it up within a home or office network you can simply follow that guide, but make sure you dont mess up your ips . If you want to connect from other locations thru the router you probably need a permanent ip4 adress and some forwarding in the router but i havent played arround with it yet. Thanks for sharing your solution Maybe this will help some ppl with similar issue. Port-Forwarding is actually quite easy, I guess if you google the model of your router you will find good guides for doing so. I dont fear the port forwarding in the router the question is, is it possible to just put the router IP into the magi.conf and use portforwarding to appear with the router ip at the Wallet because if you need to put the real ip of the connecting device into wallet.conf you need a non dynamic adress i guess. Next problem will be to connect to IP6. I will try arround if i find some time to do so. I wonder how pools connect to their wallet since they probably need to pool all the ips to one that connects to the wallet too. I still have a verry basic knowledge of this stuff and the most of the time it comes to guessing and trying things out rather than definately knowing how it does work. |
|
|
|
Can anyone explain me or give me further information on how to solo mine with other devices on a different location to the same Wallet?
Do i need to instal the Wallet on every device and import my wallet.dat to do so or is there an other option to point devices directly to it?
Following the guide by Elar, https://bitcointalk.org/index.php?topic=735170.msg17899424#msg17899424; modify magi.conf to have the following (no square brackets): rpcallowip=[IP of your PC that will run miner] restart the wallet in order to reload magi.conf, then run the miner (no square brackets), ./m-minerd --url http://[IP of your PC that runs the wallet or magid]:8232 --user magi --pass 12345 --threads 4 -e 100 This should work.
*FACEPALM*
Im stupid...
Found the issue, fixed, now it is working well thank you!Would be good to know what your actual problem was and how you fixed it. In case someone else comes accross the same problem, he would only find "I fixed it" as solution which is absolutely unhelpful in any way. The exact soulution is what joelao95 posted, the problem was that i have interchanged some of the ips... Still Facepalm. If you want to set it up within a home or office network you can simply follow that guide, but make sure you dont mess up your ips . If you want to connect from other locations thru the router you probably need a permanent ip4 adress and some forwarding in the router but i havent played arround with it yet. |
|
|
|
Can anyone explain me or give me further information on how to solo mine with other devices on a different location to the same Wallet?
Do i need to instal the Wallet on every device and import my wallet.dat to do so or is there an other option to point devices directly to it?
Following the guide by Elar, https://bitcointalk.org/index.php?topic=735170.msg17899424#msg17899424; modify magi.conf to have the following (no square brackets): rpcallowip=[IP of your PC that will run miner] restart the wallet in order to reload magi.conf, then run the miner (no square brackets), ./m-minerd --url http://[IP of your PC that runs the wallet or magid]:8232 --user magi --pass 12345 --threads 4 -e 100 This should work.
*FACEPALM*
Im stupid...
Found the issue, fixed, now it is working well thank you! |
|
|
|
|
Can anyone explain me or give me further information on how to solo mine with other devices on a different location to the same Wallet?
Do i need to instal the Wallet on every device and import my wallet.dat to do so or is there an other option to point devices directly to it?
|
|
|
|
4 things:
1) Getting a solo miner integrated into the wallet would be a great upgrade! especially for people on the Windows side. Many average Windows users know nothing about cryptocurrency at all, and to be able to just down, say let it sync, then click this button to start would tear down a major wall for Magi.
2) if anyone knows maxminers, they have been paused for 2 days now too. that is the pool i am on, personally
3) The new wallet looks great! i upgraded mine on Windows pretty quickly with the downloaded chain file.
4) I look forward to the Pine64 official wallet build!
Maxminers probably has to update the wallet maybe you can give them a hint by writing the support. Point one is exactly what i mean, the mainstream computer user likes simple setups, sliders, buttons and those stuff in addition with a feeling of control provided by showing some data like the pool dashbords do. |
|
|
|
when you are on poloniex and so many other exchanges what is the point of worrying about bittrex? if they dont see the value in having magi listed there or need to have .5 BTC trading a day happening then that is honestly not the XMG communities problem. Anyway, it would be great to still be listed on as many exchanges as possible, but my point is that bittrex does not make or break the project so it's difficult for me to really care enough to do anything.
I have a similar feeling, it feels a little greedy IMHO - I know they need to make a profit - however most other exchanges don't have such steep rules on volume and are making good profit, makes it difficult for smaller coins to exist on there - quite a lot of smaller coins are using robots on the exchange just to keep the volume up - doesn't seem honest to me. It it goes - it may be a good thing for cryptopia and nova. for someone it is good and for someone it will be bad experience but according to its use only. I'm in the process of writing a trading robot - hopefully when its ready it'll help to increase volume on Trex a bit more (however only supports Polo to start with) If you need a Beta tester give me a hint, sounds interesting. Constant candles every 5 minutes will support acceptance a lot i guess since more people start to play arround with it than. Also a integrated Miner GUI in the Wallet to solo mine would lead a lot people to join the community i guess, since the m7m is very nice for mining on smaller devices. A general problem of crypto at the moment when it comes to mining is that about 90% of the world wide computer users are just normal people that dont know much about computers at all. For all of us here it is no problem to set up minerd read a bit how to solve things and get it running as we would like to have it running. Some workmates for example have seen me recently while trading on polo on my workplace and where like " oh your'e trading crypto i heared a lot about that but i dont know how this works and i gave up since i don't get it to run". People are always cought in they're confortzone and have a hard day to break out of it. With the posibility to mine with an clear and self explaining GUI like the Wallet has, or at its best a integrated mining funtion within the wallet could do something that every crypto lacks at the moment to get more simple people into crypto. Since Magi is mainly a currency to pay with it needs long term a wide userbase because merchants will always ask themself "how many more volume of sales will we have by accepting this currency because there are people not buying at the moment because magi is not accepted". In addition to this merchants always need a stable priced currency to avoid the risk of an total loose of the trade margin or even more. In my opinion Magi is a great projekt but lacks marketing and a well designed hompage at the moment. Unfortunately i only know stuff about selling things coaching people to leave there confortzone and get to a selling machine on theyr'e job but not about programming and web design. But if you want further ideas and thoughts about the projekt give me a hint and i will try to figure things out. I also can do a german translation for the wallet if you want to, since it is pretty much mixed german, english at the moment. |
|
|
|
There is only a yay !!! if you find a block while solomining i guess. Everything else wouldnt make a sense to me. Maybe you can helph me with solomine setup since im trying to use this guide for litecoinqt to get to work with magiqt. https://bitcointalk.org/index.php?topic=83371.0EDIT Okay, got it to work no errors so far with one exception im getting [2017-02-18 16:35:17] No payout address provided, switching to getwork too. Maybe some one of the pool owners around here knows ho to fix ? EDIT Regards! Hello, I searched a bit and find a thing about the payout address error and it seems we can ignore this error, nothing really helpful about the 500 Internal Server Error but how far I can go in the putty screen I don't had this error in the last hour anymore. it's not really hard to set up the miner, if it can help anyone : I have made an user account for mining, so all the following things are to do in the /home folder of your user download this miner https://github.com/magi-project/m-cpuminer-v2/releases and the wallet http://coinmagi.org/bin/m-wallet-1.3.1/ Extract the 2 downloaded files and navigate to m-wallet-1.3.1-linux/conf/ and copy the magi.conf file in /home/user/.magi and edit it, I've added daemon=1 in it and put a rpcuser and password, my magi.conf file looks like this daemon=1 server=1 listen=1 rpcuser=magi rpcpassword=12345 rpcport=8232 rpcallowip=127.0.0.1 # Add nodes to connect to specific peers addnode=104.128.225.215 addnode=104.128.225.240 addnode=104.128.225.241 addnode=104.131.42.100 addnode=216.189.144.186 addnode=216.189.144.211 addnode=216.189.144.212 # posii=0 to disable PoS staking; default = 1 posii=1 # Transaction under stake with a value greater than the threshold is being splitted stakesplitthreshold=500 # Transactions with values less than the threshold will combine into one stakecombinethreshold=250 Then navigate to m-wallet-1.3.1-linux/bin/64/ and start the daemon with ./magid & and let him a few hours to download the blockchain. To launch the miner just navigate to the m-minerd-64-linux folder and start the miner with ./m-minerd --url http://127.0.0.1:8232 --user magi --pass 12345 --threads 4 -e 100 This is exactly what I did, change the folders names and the --user and --pass according to your configuration. It will default to a new address in your wallet, once you find a block it will show up.
Edit - I'll add this, there is a massive solo miner on now and the hash rate jumped to 137Mhs, us small solo miners don't stand a chance at this point. Every pool I can see is still stuck and not finding any blocks for more than a day now. Still going up, 148Mhs now.
I have found the wallet.dat in the .magi folder, i copied it to my pc to check if he finds a block I was mining with my home computer in the pom.m-hash pool, since nearly 2 days no blocks, no more update in the confirmed and unconfirmed balance, it is due to the big miner too ? Probably they havent done the update to the new wallet yet. I also have some trouble with them it seems like something or someone is not working proper there. "the big miner" was probably https://xmg.suprnova.cc that was back from maintenance around that time. There are some smaller pools back from maintenance too maybe you would like to point your device to them. |
|
|
|
Hello,
I just registered here,
I try to solo mining on a vps, debian 8, for test before I setup this on my dedicated server. I want solo mine into the server wallet and stake too 24/24 to support the network.
The miner works great for pool mining, but when I try to solo mine I have a lot of errors :
HTTP request failed: The requested URL returned error: 500 Internal Server Error
json_rpc_call failed, retry after 30 seconds
When he start mining i have another error : No payout address provided, switching to getwork.
I think the first errors appears, for ~30 min, because magid is starting and syncing the blockchain, after the miner starts to show me the hashrate of the 4 threads, so I think he is mining but he doesn't say (yay !!!) like when pool mining and i have regularly the errors who comes back for 5-10 min and sometimes only 1 error then a few hashes then 1 or 2 errors again or more...
I don't know if he is really mining anything and why i have this error. I hope anyone here could answer to my questions and help me to get this working.
There is only a yay !!! if you find a block while solomining i guess. Everything else wouldnt make a sense to me. Maybe you can helph me with solomine setup since im trying to use this guide for litecoinqt to get to work with magiqt. https://bitcointalk.org/index.php?topic=83371.0EDIT Okay, got it to work no errors so far with one exception im getting [2017-02-18 16:35:17] No payout address provided, switching to getwork too. Maybe some one of the pool owners around here knows ho to fix ? EDIT Regards! It will default to a new address in your wallet, once you find a block it will show up. Edit - I'll add this, there is a massive solo miner on now and the hash rate jumped to 137Mhs, us small solo miners don't stand a chance at this point. Every pool I can see is still stuck and not finding any blocks for more than a day now. Still going up, 148Mhs now. The biggest pool https://xmg.suprnova.cc is back since a few hours. |
|
|
|
|
