Bitcoin Forum
September 26, 2025, 11:25:15 AM *
News: Latest Bitcoin Core release: 29.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] on: February 15, 2021, 11:25:44 AM
I don't remember how this was fixed in the past. Any idea if it will be fixed?

In the past it was fixed by syncing to only Joes node that was defined as the right chain.

As Joe doesn't seem to care anymore we need a different solution this time.

By digging a little into my logs the current problem is that the nodes ban each other constantly.

I was able to get on the longest chain by adding
Code:
banscore=10000
bantime=120
to my magi.conf, close the wallet, deleting peers.dat and restarting it.

it doesn't prevent others banning you, but it prevents you from disconnecting from other nodes.
2  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] on: March 21, 2020, 05:47:20 PM
I read about attacks on the network before, but until now I hadn't been affected.
That changed now and from the logs, this is what happened:

Within a relatively short amount of time I lost all my peers and my wallet is unable to reconnect to the network.

I'm not sure if that's the same problem other people are facing.

I think you are banned for a period of 24 hours, because the algo finds you're misbehaving.
You can try to connect from a computer with another ip to check.
This happens to me once in a while.

I think the exact opposite is the case. It disconnects other nodes right after I received a block. However, the result is the same: I'm disconnected.
In the meantime I'm once again connected without changing anything and all is running fine.
3  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] on: March 21, 2020, 07:46:53 AM
I read about attacks on the network before, but until now I hadn't been affected.
That changed now and from the logs, this is what happened:

Code:
received block f190cb6bd110e1b03a17
Misbehaving: 95.217.73.169:8233 (0 -> 100) DISCONNECTING
disconnecting node 95.217.73.169:8233
ERROR: ProcessBlock() : block with too little proof-of-stake
received block 000000002ada6782f29a
SetBestChain: new best=000000002ada6782f29a317813ea7eb16cba7bac99443bf848d9e385157e1c82  height=2565305  money supply=10386445  trust=72883134418294  date=03/21/20 07:06:46
Stake checkpoint: fee594c6
ProcessBlock: ACCEPTED
ProcessSyncCheckpoint: sync-checkpoint at b9a74f34b94ec9b632843129ef84d32b42c12f47840b16197fa62b79fed6a5c0
ProcessSyncCheckpoint: sync-checkpoint at 04ba2532e91c606627dc492a589e3ec19d900f625e97bd8577cee1231435b3b7
getblocks -1 to 00000000000000000000 limit 500
received block 0000000029faf1868395
Misbehaving: 104.128.225.241:8233 (0 -> 100) DISCONNECTING
disconnecting node 104.128.225.241:8233
ERROR: ProcessBlock() : block with too little proof-of-work
ProcessSyncCheckpoint: sync-checkpoint at 064ee326d5649a00e88b66ac7c05054cfabfa9ba1dec5798e1697ee603758239
received block f190cb6bd110e1b03a17
SetBestChain: new best=f190cb6bd110e1b03a17b2076620de21642176c085f062bd4f9607618f16bde6  height=2565306  money supply=10386445  trust=72883135485596  date=03/21/20 07:06:56
Stake checkpoint: 82fdb70e
ProcessBlock: ACCEPTED
received block 00000000147d32381e34
Misbehaving: 104.128.225.215:8233 (0 -> 100) DISCONNECTING
disconnecting node 104.128.225.215:8233
ERROR: ProcessBlock() : block with too little proof-of-work
ProcessSyncCheckpoint: sync-checkpoint at 7915b1678c3b18dab0ae69776d53ae462d4e7b244eecab92833671fc157279f3
received block 000000007a9c648535f0
Misbehaving: 85.214.23.202:8233 (50 -> 150) DISCONNECTING
disconnecting node 85.214.23.202:8233
ERROR: ProcessBlock() : block with too little proof-of-work
ProcessSyncCheckpoint: sync-checkpoint at 757b4ac3ee35ce3eaef235b3ec2dc8360d1805b0a56ab7839f7baadd99cab1a5
received block 00000000147d32381e34
Misbehaving: 51.77.152.160:8233 (0 -> 100) DISCONNECTING
disconnecting node 51.77.152.160:8233
ERROR: ProcessBlock() : block with too little proof-of-work
received block 0000000029faf1868395
SetBestChain: new best=0000000029faf1868395d2812c078e44289c918d5c9bc793b3a6c43d18a24ef1  height=2565307  money supply=10386480  trust=72883135490508  date=03/21/20 07:07:57
Stake checkpoint: 9dce6d97
ProcessBlock: ACCEPTED
received block 793a9c947062305422ff
ProcessBlock: ORPHAN BLOCK, prev=000000007a9c648535f0
ProcessSyncCheckpoint: sync-checkpoint at 78bc95314fab214ed782c7f0b0b8503eb01242c88e14cf87b510f9014e807ec7
ProcessSyncCheckpoint: sync-checkpoint at f8446430d0f09865c48fdd43bea1c90b85239e68e8228c880e7adef39dd1b219
received block 00000000153334a21ff2
Misbehaving: 163.172.122.60:8233 (0 -> 100) DISCONNECTING
disconnecting node 163.172.122.60:8233
ERROR: ProcessBlock() : block with too little proof-of-work
ProcessSyncCheckpoint: sync-checkpoint at b1381e8fdc5893220f7a3f251ff9fcf4baf500f90ea2411b08c0dbcf7c996fe6
received block 00000000616835e0b967
ProcessBlock: ORPHAN BLOCK, prev=00000000153334a21ff2
received block 000000007a9c648535f0
Misbehaving: 104.131.5.234:8233 (3 -> 103) DISCONNECTING
disconnecting node 104.131.5.234:8233
ERROR: ProcessBlock() : block with too little proof-of-work

Within a relatively short amount of time I lost all my peers and my wallet is unable to reconnect to the network.

I'm not sure if that's the same problem other people are facing.
4  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] on: February 20, 2020, 06:56:29 PM
Their official announcement can be read here:
https://tradesatoshi.com/News/476/Tradesatoshi-Is-Closing-Down
5  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] on: September 18, 2019, 02:49:47 AM
Then I ran magid:
$magid -daemon
Magi server starting


Okies, cool, let's check its head:
$ magid getinfo
error: couldn't connect to server

 Huh

It's running now but I can't seem to interact with it and the debug.log keeps growing, when it was smaller its entries seemed to indicate magid was scanning the blockchain data which was bootstrapped earlier. Now, 12hrs later, debug.log is ~27MB and I still can't interact with magid.

I'm not sure, but to me it seems like magid is syncing the blockchain over the network from scratch (you're about 800k blocks from the top away).
So i guess something went wrong with using the bootstrap-file and it would explain why it's taking that long.
During syncing you can't interact with it via the rpcport.

"magid --help" lists all commands to startup magid and is not the same as
"magid help" which lists you all available rpc commands, once it's finished syncing.

"magid help walletpassphrase" tells you:

walletpassphrase <passphrase> <timeout> [mintonly]
Stores the wallet decryption key in memory for <timeout> seconds.
mintonly is optional true/false allowing only block minting.
6  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] on: August 22, 2019, 08:38:14 PM
I have 4 different wallet.dat which I backed up from 2016 but now I am worried to try anything. Can you tell me where I should look in the GUI?
Also, as the blockchain is fully downloaded and wallet is syncronized, is it safe for me to shut wallet down and try the different wallet.dat? If so, where would I look to see if I get access to both my addresses?
It's safe to use a different wallet.dat, but don't forget to backup your current one! Just to be safe I'd only change it to a copy of the one you want to try out.
After you've changed it I'd suggest to type "repairwallet" into the console. It might reveal the missing address.
You can check that with "getaddresses" in the console or in the receive tab.
For the future: to reset the coin age it's possible to send the coins directly to the same address were they are coming from. No need for a different address or even wallet!
7  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] on: April 16, 2019, 10:54:26 PM
https://chainz.cryptoid.info/xmg/tx.dws?921a5b2ea9fd9da40d8f7d02d47b27b3bf63835025b6584d04aeebb25f308e8f.htm

   
Not yet redeemed   9G1MNnbqVdxth5Z7UuNn9V88BsCqvP9yei   100.00080584 XMG


What this mean...

I have lost my coins??

It means that the coins arrived in that wallet and haven't been used for anything (eg. sent to another wallet or staked) since.
It's absolutely nothing to worry about.
8  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] on: April 11, 2019, 12:02:27 AM
You get this message if your wallet isn't unlocked for staking, your chain isn't synced or it's disabled in the config.
To unlock your wallet for staking go to the menu "Mint->Enable mPoS Minting".
If you've changed settings in your config file you have to restart the wallet.
Coins get to old for staking around 10k confirmations, so you're fine there.
9  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] on: December 13, 2018, 03:00:30 AM
I worked out a while ago that you needed about 15,000 XMG to generate one XMG per day - however the rate has dropped a lot since some changes in the spring - I'm no longer able to work it out as it fluctutates a little

It's now 20,000 XMG (in chunks between 750-1000) to generate one XMG per day.


What you're experiencing here is the variable interest rate of staking coins. As far as i can tell there wasn't a change in the code, rather than the amount of staked coins.
I haven't looked into the code, but in general there's evidence that the amount of staked coins directly influences the interest rate.
I've started tracking the magi metrics sometime back in February and as you can see on the following graph the more coins are staking the higher the interest rate:


To know how many coins you need to gain 1 Magi per day is quite simple to calculate:
coins needed =  1 / ( stakeinterest / 365 )

you get the current interest rate with the "getmininginfo" method of the magid client. (Users of the GUI-wallet can type in that command in the last tab).
Just notice that numbers changes quite frequently, so you might take a average of the returned values.
I smoothed the following graph and your values seem to fall into that range;


From my experience staking 100-200 coins is the minimum you should try. below that you probably run into the problem that your coins age faster than they gain weight. As mentioned by others before the sweet-spot seems to be around 500-1k coins
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!