Is it possible to increase the transfer limit (back to what it was), it is a bit ennoying how it is (especially as I don't know what is the limit but I know that I had to split some deposit and even while transfering to one address in my wallet)
Is that something "Transaction creation failed" error? if so that could be due to a large number of inputs used to create transaction especially when sending a big amount of coins. |
|
|
|
|
I just thought of a simple way to calculate average diff. You can simply sum up diff of past 100 blocks and then divide it by 100, which is a simple average. This way won't differ much than the actual value; this method should be better than using the diff-V2 since for mining calculator, the more stable value, the better.
|
|
|
|
Alright, we need a little figure on this. What needed are recent 2000 blocks' difficulty and also noticed the block time used in calculation too. So most straightforward is to access the wallet's api then; either, let me look into hosting a JSON API in my server to access block value. Are you trying to add a mining calculator? http://www.altcoinprofitability.com  {
"hashrate (kh/s)" : 100.00000000,
"difficulty" : 1.26654813,
"difficulty(aver)" : 2.29402066,
"blockvalue" : 2.52426217,
"mining (XMG)" : {
"1 hour" : 0.09223161,
"1 day" : 2.21355856,
"1 week" : 15.49490990
}just another option. |
|
|
|
Hm, what do you need? Let me know specs so that I can make a custom API call if you want?
A custom API (json?) that returns the current difficulty and the reward ? My goal is to add XMG on my site  Will this work for you?  getnewblockvaluebynumber 174196 {
"flags" : "proof-of-work",
"difficulty" : 2.40458289,
"difficulty-V2" : 1.66967352,
"blockvalue" : 12.39547783
}difficulty is the actual value; difficulty-V2 is the value calculated by https://github.com/magi-project/magi/blob/master/src/main.cpp#L968, i.e., rDiff as in the formula I posted. |
|
|
|
Hi,
Who knows the formula to calculate the block reward ?
Ty
 I missed this too. This is the formula basically: 50. * pow( (5.55243*(exp(-0.3*rDiff/0.39*M7Mv2_move) - exp(-0.6*rDiff/0.39*M7Mv2_move)))*rDiff, 0.5)
/ (3.02849*exp(-M7Mv2_move / 0.14814) + 1.794*exp(-M7Mv2_move / 0.89044) + 0.74536)
/ (1 + exp(rDiff/(0.16/M7Mv2_move) - 2.2 / M7Mv2_move / (0.16/M7Mv2_move))) M7Mv2_move is something to move the optimum hashrate (where gets maximum 50 XMG) forward over time. The most important is rDiff which is rather a simple taking of the difficulty, but depends on the history of difficulties. https://github.com/magi-project/magi/blob/master/src/main.cpp#L968 is the actual implementation; a demonstration how it looks is shown in https://bitcointalk.org/index.php?topic=735170.msg9991269#msg9991269 (the blue curve). Ty Ok i can't calculate it myself  Hm, what do you need? Let me know specs so that I can make a custom API call if you want? |
|
|
|
Joe, I was asked on Twitter and I'm not sure what about this block: Generated but not accepted means orphan blocks (he is solo mining). But why does it have a green tick? My orphan PoS blocks have a blue ? instead of a green tick. Or is there a difference between PoW and PoS? http://prntscr.com/632oq2What I can see from the image the green tick is transferred amount, not staked; while all those with question mark are PoS; that's weird, none of them accepted, is wallet the latest version? Yes, he said he's solo mining and found this block. You mean he's probably on the wrong fork? Last night, he updated from the 1.1.0.1 to v1.2.1.2 EDIT: The PoS blocks were generated with the old wallet, might be the reason they were not accepted. EDIT2: Now the PoW block has been accepted. Not sure what happened, probably the new wallet wasn't fully synced. PoS works now, too. All fine. Glad that works. |
|
|
|
Hi,
Who knows the formula to calculate the block reward ?
Ty
I missed this too. This is the formula basically: 50. * pow( (5.55243*(exp(-0.3*rDiff/0.39*M7Mv2_move) - exp(-0.6*rDiff/0.39*M7Mv2_move)))*rDiff, 0.5)
/ (3.02849*exp(-M7Mv2_move / 0.14814) + 1.794*exp(-M7Mv2_move / 0.89044) + 0.74536)
/ (1 + exp(rDiff/(0.16/M7Mv2_move) - 2.2 / M7Mv2_move / (0.16/M7Mv2_move))) M7Mv2_move is something to move the optimum hashrate (where gets maximum 50 XMG) forward over time. The most important is rDiff which is rather a simple taking of the difficulty, but depends on the history of difficulties. https://github.com/magi-project/magi/blob/master/src/main.cpp#L968 is the actual implementation; a demonstration how it looks is shown in https://bitcointalk.org/index.php?topic=735170.msg9991269#msg9991269 (the blue curve). |
|
|
|
Joe, I was asked on Twitter and I'm not sure what about this block: Generated but not accepted means orphan blocks (he is solo mining). But why does it have a green tick? My orphan PoS blocks have a blue ? instead of a green tick. Or is there a difference between PoW and PoS? http://prntscr.com/632oq2What I can see from the image the green tick is transferred amount, not staked; while all those with question mark are PoS; that's weird, none of them accepted, is wallet the latest version? |
|
|
|
Don't worry it's there!  BTW Magi is working on online wallets! Now on 6! Going up!  Im in too Nice! More people in that group gives Magi the change to go up in the group list also! Added to OP. |
|
|
|
- I will consider speeding PoW blocks generation up in the future since it took 10 hours to distribute coins on new blockchain. This does not seem right.
hm, not sure of this you meant 10 hours is too long? I'd assume this is regarding the premine which can be done before releasing the formal code; though it takes time (only at the beginning I'd say), the block chain will be more secure. Yes, this is an option. Another one could be to make PoW blocks being mined more often at the very beginning and then slower after some time. This will be a perfect solution to me. Here is a mac os wallet I just compiled if anyone using mac wants to do the test. http://coinmagi.org/files/Noblecoin/Noblecoin-Qt.dmg |
|
|
|
Magi (XMG) marketingteam is looking for people who speak the following languages: Portuguese, Chinese = done, Japanese, Indonesian = done, Spanish, Romanian, French, Korean.
Magi (XMG) marketingteam is also looking for a suitable poker site that accepts Cryptos.
Marketingteam also welcomes any information from the community about possible extensions and wishes of or for XMG!
if you can help it send me pm.
Thank you Dsyahputera for the new up to date Indonesian Magi thread! Dev can you add this one in the originel OP? https://bitcointalk.org/index.php?topic=948443.0Also this one pls: new Chinese Magi thread: https://bitcointalk.org/index.php?topic=901516.0Made the modifications to OP. |
|
|
|
Uhm the newest wallet download contains a older version, might be the reason why my wallet is not syncing :/
With one you mean and where did you get it from? I guess it's ok, inside the app it says it's 1.2.1.2 but unter preferences for the file it says 1.2.1.1 or so. Redownloading the chain again... Guess your problem has solved; any version of 1.2.0.1 and above will be working just fine. The wallet will take time to find nodes initially; you can specify nodes by adding the following content to magi.conf file, in case any one else needs those too: addnode=104.128.225.215
addnode=216.189.144.213
addnode=162.245.217.165
addnode=104.131.57.65
addnode=104.131.42.100 |
|
|
|
Warning: Do not deposit any coins to exchange betasharex.com
Many users complained that their deposits will not get credited to your account and withdrawals don't work, too. Support doesn't reply to tickets or mails. We've removed them from the OP, they are no longer a recommended exchange.
Deposit/trade at your own risk!
Thanks for heads up; I have removed it from OP until people make me suggestion to get it back on the list. |
|
|
|
- I will consider speeding PoW blocks generation up in the future since it took 10 hours to distribute coins on new blockchain. This does not seem right.
hm, not sure of this you meant 10 hours is too long? I'd assume this is regarding the premine which can be done before releasing the formal code; though it takes time (only at the beginning I'd say), the block chain will be more secure. |
|
|
|
Hello Noble people!
The mainnet tests are officially open
Looks great, I'll be looking into it. @others, feel free to point out any concern regarding PoS-II; what's in the code is mostly my 'thinking'; I might give more details addition to prior post. We are still able to tune the PoS a little bit (if any) safely after test I'd say of course if you guys want to do that. |
|
|
|
So my CPU is not running at 100% hashrate? Do you have one to test it? I don't have one myself. I would certainly have a look at CPU core temperatures to see if thermal throttling was an issue. The miner pushes a CPU to the limit. I ment hefty with the testing part https://i.imgur.com/GODFMDk.png --> as you can see it shows me 100% + OC merge this cpu that bobben2 have is only a little faster cpu than yours there shouldnt be more than 2-3 khash difference and this is what bobben2 posted Hefty, I have one i5-4460 Has(h)well on ubuntu 12.04. It does ~81kh/s @ -t 4 at stock freq, stock cooler, temp goes up to 65 deg. so it seems that ubuntu is yielding so much more hash than win 7, 8.1 also i have different hash today than few days ago on same exact machines, differences of 2-3 khash it will be so hard to pinpoint exact hash for any cpu right now. Only by starting simple ap like cpuz while hashing will lower your hash by 1khash on some systems so many things like different mobos etc can give you so many different results. I will need to make at least 2 separate lists for linux and windows bc for now what im getting from other users difference is so big between different os to calculate they hash together. It might be normal with a few percentage difference in the hashrate, which relies on many factors. Given mining under the same minerd, like Spexx's compilation, we may summarize with average values along with some percentage of uncertainties. Making separately for linux and windows would make you a bit tough work on the listing, but feel free to do so. Btw right now I'm taking bobben2's course to optimize the miner. I guess we can get the hashrate data "consistently" right now. By having another optimized miner, things will go wild varying for sure. |
|
|
|
|
Show Posts
