Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 466. (Read 2375638 times)

agree. same case. been a supporter too.

most updated

Where to find the most updated information?

master not ready, yep

Hi amigo,
You are right. Think we al have to wait just a little more.
After that we as community have to think about the extending the Magi team. Magi has grown bigger & bigger in de last 2,9 year. It deserves a bigger team to be able to handle all things good and continues building a great future.
So if people have ideas about this inform us here or pm

Not yet. But received message pm that it will be paid sometimes these days and that the campaign is finished.

Did anyone received the last weeks reward yet?

https://bitcointalksearch.org/topic/closedcoin-magi-xmg-signature-campaign-2032993

Guys what's the current state of the blockchain? I participated in solo mining earlier in the week however that was lost due to the hardfork to 'fix' the accidental fork. Now I look again and once more the supranova pool is down and my wallet won't sync. I downloaded the new build, purged my databases and resynced.  

I've been a supporter of Magi and mining on and off since 2015 - I can't believe what has happened this week  

I think we are really stretching our credibility with our users and exchanges.

If thats the version Joe is working on than best thing is waut until he is finished. 

the latest update seem to be broken now?

# make -f makefile.unix
/bin/sh ../share/genbuild.sh obj/build.h
g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -I/home/src/magi/src -I/home/src/magi/src/hash -I/home/src/magi/src/obj -I/usr/local/BerkeleyDB.4.8/include  -DUSE_UPNP=0 -DUSE_IPV6=1 -I/home/src/magi/src/leveldb/include -I/home/src/magi/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -msse2 -MMD -MF obj/main.d -o obj/main.o main.cpp
In file included from magirpc.h:16:0,
                 from main.cpp:16:
json/json_spirit_writer_template.h: In function ‘String_type json_spirit::non_printable_to_string(unsigned int)’:
json/json_spirit_writer_template.h:31:50: warning: typedef ‘Char_type’ locally defined but not used [-Wunused-local-typedefs]
         typedef typename String_type::value_type Char_type;
                                                  ^
main.cpp: In member function ‘bool CBlock::AcceptBlock()’:
main.cpp:2708:25: error: ‘nHeight’ was not declared in this scope
     if (IsBlockVersion5(nHeight) && nVersion < 5)
                         ^
main.cpp:2730:132: warning: format ‘%d’ expects argument of type ‘int’, but argument 2 has type ‘int64 {aka long long int}’ [-Wformat=]
         return DoS(50, error("AcceptBlock() : coinstake timestamp violation nTimeBlock=%d nTimeTx=%u", GetBlockTime(), vtx[1].nTime));
                                                                                                                                    ^
main.cpp: In function ‘CBlock* CreateNewBlock(CWallet*, bool)’:
main.cpp:4530:89: warning: format ‘%lld’ expects argument of type ‘long long int’, but argument 2 has type ‘unsigned int’ [-Wformat=]
             printf("@CreateNewBlock -> txCoinStake.nTime=%"PRI64d"\n", txCoinStake.nTime);
                                                                                         ^
main.cpp:4543:90: warning: format ‘%lld’ expects argument of type ‘long long int’, but argument 2 has type ‘unsigned int’ [-Wformat=]
    printf("@CreateNewBlock-PoS found -> txCoinStake.nTime=%"PRI64d"\n", txCoinStake.nTime);
                                                                                          ^
In file included from hash_magi.h:5:0,
                 from main.h:13,
                 from db.h:8,
                 from main.cpp:8:
magimath.h: In function ‘double exp_n2(double, double)’:
magimath.h:46:1: warning: control reaches end of non-void function [-Wreturn-type]
 }
 ^
makefile.unix:187: recipe for target 'obj/main.o' failed
make: *** [obj/main.o] Error 1

Hi guys,

While coin is sick I want ask developers one question:

This info from cheat sheet:


1) question  6 mo, 1 year later... 5 year latter from what time?
What is actual  hashrate values.


2)  If i have some hash rate, for example 20-30 Mh/s  (or even more 50-70% of overal hashrate)  and start mining,  everyone in network will get <1 XMG block..
So - I can wait until others stop mining, because it is not profitable and then slow-down my power and collect jackpot coins?  How network defends from such attacks?
Or it is not attack but just a strategy and legal?

Pools are waiting for updates & not open at the moment

Is suprnova pool working for you? Cannot connect to it... Also last block was found 16 hours ago. What's the best alternative to suprnova?
Thank you.

I think u misunderstood the concepts of general practice of giving updates. Nothing can be said for certain because u dont know whether that kind of event happened or its planned or still undefined. I will always keep saying that and only a handful of facts could be analyzed and used in composing the table of possible outcomes.

I know, I see the same in my logs but from other ip's.

Thats good news Joe!
All hold actions after the posts from Joe.
Btw tonight for Joe is 6 hours later than Europe so give him the time.Thanks

I will make updates tonight whenever back from work.

this network is stuckm,  213.32.21.37 poolinfo.systms.org

send version message: version 71051, blocks=0, us=95.211.209.73:8233, them=213.32.21.37:59018, peer=213.32.21.37:59018
receive version message: version 71061, blocks=1444963, us=95.211.209.73:8233, them=213.32.21.37:8233, peer=213.32.21.37:59018
Added 1 addresses from 213.32.21.37: 8 tried, 109 new
Misbehaving: 213.32.21.37:59018 (0 -> 100) DISCONNECTING
disconnecting node 213.32.21.37:59018
connection from 213.32.21.37:59184 dropped (banned)
connection from 213.32.21.37:59304 dropped (banned)
connection from 213.32.21.37:59384 dropped (banned)
connection from 213.32.21.37:59474 dropped (banned)
connection from 213.32.21.37:59590 dropped (banned)
connection from 213.32.21.37:59690 dropped (banned)
connection from 213.32.21.37:59782 dropped (banned)

I have and also purged blockchain and loaded the d/l one from Joe.

Wallet will not maintain a connection. Constantly connects n disconnects,

A quick recap to help others: -

To check your wallet is on the correct chain
You can type getblockcount under console to check to see if you are up to the correct block and compare against https://poolinfo.systms.org/#magi

To resync the blockchain
- Backup your wallet.dat
- Exit from m-wallet.exe
- Add oVPN's list to %Appdata%\magi\magi.conf (create the file if it doesn't exist)
- Delete your blocks, database, .lock and peers.dat files
- Download the blockchain and extract to your magi folder from http://coinmagi.org/bin/block-chain/
- Run m-wallet.exe (version 1.4)

If you are missing coins
Type repairwallet under console (make sure you have a backup of your wallet.dat)

Sample magi.conf