<<  >> (p.1092)
    Author Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay]  (Read 2377228 times)

    • starcrys
    Newbie
    *
    Offline Offline

    Activity: 27
    Merit: 0


    View Profile
    January 06, 2018, 02:47:05 AM
     #21821
    Quote from: buckonz on January 06, 2018, 02:28:45 AM
    Quote from: starcrys on January 06, 2018, 02:17:55 AM
    Erm...Can anyone help me on enabling staking? I've put "staking=1" and "posii=1" (with out the " ") in the magi.conf but the wallet still shows not staking (only those 2 commands were input)... Can someone help me on where I've gone wrong? Thanks.

    Have you specifically unlocked your wallet for staking?

    magid walletpassphrase YOUR_PASSWORD 9999999 true

    Yup, I have unlocked the wallet through the client by inputting the passphase. The command "magid walletpassphrase YOUR_PASSWORD 9999999 true" doesn't seem to be working when I put it in the conf file. It's still showing up as not staking. Do I have to input all the other stuff like rpcuser, rpcpassword, rpcport, server, listen, rpcallowip, addnode?

  • Foo_Plinger
    Newbie
    *
    Offline Offline

    Activity: 31
    Merit: 0


    View Profile
    January 06, 2018, 02:51:45 AM
     #21822
    Did you check the magi.conf at %appdata%\magi

  • buckonz
    Newbie
    *
    Offline Offline

    Activity: 25
    Merit: 0


    View Profile
    January 06, 2018, 02:52:54 AM
     #21823
    Quote from: starcrys on January 06, 2018, 02:47:05 AM
    Yup, I have unlocked the wallet through the client by inputting the passphase. The command "magid walletpassphrase YOUR_PASSWORD 9999999 true" doesn't seem to be working when I put it in the conf file. It's still showing up as not staking. Do I have to input all the other stuff like rpcuser, rpcpassword, rpcport, server, listen, rpcallowip, addnode?

    What I provided was a command line, not a configuration option.  I'm running the Magi Daemon.

    Before I ran this command, using 'magid getinfo'...

    "paytxfee" : 0.00010000,
    "unlocked_until" : 0,
    "errors" : ""

    ...and after running the command:

    "paytxfee" : 0.00010000,
    "unlocked_until" : 1525207002,
    "errors" : ""

  • jonathin.r
    Member
    **
    Offline Offline

    Activity: 98
    Merit: 11


    View Profile
    January 06, 2018, 03:04:36 AM
     #21824
    Quote from: orcan1ce on January 06, 2018, 02:40:38 AM
    Is there anything we need to do after the hardfork?

    Update your wallet, and make sure your miner(s) are configured properly. Otherwise, you're good to go!
    My XMG Address: 9LzxHqsxrRPMCyBffjMc3cLuB5hwEG5Ufq
    "Un pour tous, tous pour un" - The Three Musketeers, 1844

  • s0litaire
    Member
    **
    Offline Offline

    Activity: 133
    Merit: 15


    View Profile
    January 06, 2018, 03:22:44 AM
     #21825
    Quote from: buckonz on January 06, 2018, 01:30:47 AM
    Quote from: ParaplegicRacehorse on January 06, 2018, 01:24:23 AM
    make sure you are in the directory where you compiled the software. './m-minerd --help' or './m-minerd --benchmark'

    Basically, './m-minerd <list_of_arguments>'

    alternatively you could 'sudo make install' and that will move the binary tousr/bin/m-minerd and it will always be available just by 'm-minerd' so you don't need to enter any path statements when you run it.

    Thanks for the prompt response. I believe that I am attempting to run the software from the correct location. However I suspect I have the syntax incorrect:

    odroid@odroid:~/m-cpuminer-v2$ ls -a
    .                configure.ac          magimath.cpp           m_minerd-sha2.o
    ..               COPYING               magimath.h             m_minerd-util.o
    aclocal.m4       cpu-miner.c           Makefile               NEWS
    AUTHORS          cpuminer-config.h     Makefile.am            nomacro.pl
    autogen.sh       cpuminer-config.h.in  Makefile.in            README
    .autogen.sh.swp  depcomp               miner.h                scrypt-arm.S
    autom4te.cache   .deps                 missing                scrypt.c
    ChangeLog        Dockerfile            m-minerd               scrypt-x64.S
    compat           elist.h               m-minerd.1             scrypt-x86.S
    compat.h         example-cfg.json      m-minerd.bat           sha2-arm.S
    compile          .git                  m_minerd-cpu-miner.o   sha2.c
    config.guess     INSTALL               m_minerd-m7mhash.o     sha2-x64.S
    config.log       install-sh            m_minerd-scrypt-arm.o  sha2-x86.S
    config.status    LICENSE               m_minerd-scrypt.o      stamp-h1
    config.sub       m7                    m-minerd.sh            util.c
    configure        m7mhash.c             m_minerd-sha2-arm.o
    odroid@odroid:~/m-cpuminer-v2$

    Any other instructions needed for the 'sudo make install' instructions? Do I just use this from within the same file structure?

    You can use it from there. but you might need to use the full path if you are going to use it in scripts:
    ~/m-cpuminer-v2/m-minerd <arguments>

  • buckonz
    Newbie
    *
    Offline Offline

    Activity: 25
    Merit: 0


    View Profile
    January 06, 2018, 03:39:37 AM
     #21826
    Quote from: s0litaire on January 06, 2018, 03:22:44 AM
    You can use it from there. but you might need to use the full path if you are going to use it in scripts:
    ~/m-cpuminer-v2/m-minerd <arguments>

    I ended up using the 'sudo make install' so now I can essentially run it from anywhere. I managed to get it going. However as I mentioned in a recent post, it struggles to maintain a connection to the BULL MINING pool.

    [2018-01-06 16:17:52] thread 6: 26396 hashes, 1.66 khash/s
    [2018-01-06 16:18:22] Stratum connection failed: Connection timed out after 30000 milliseconds

    ...and it didn't connect again until...

    [2018-01-06 16:32:43] ...retry after 30 seconds
    [2018-01-06 16:34:41] thread 4: 91742 hashes, 1.58 khash/s

    It stayed up for about 7 minutes and then starting having Stratum connection issues again!?  *sigh*

  • ParaplegicRacehorse
    Member
    **
    Offline Offline

    Activity: 79
    Merit: 36

    HODL. Patience.


    View Profile
    January 06, 2018, 03:46:52 AM
     #21827
    Quote from: buckonz on January 06, 2018, 03:39:37 AM
    [2018-01-06 16:32:43] ...retry after 30 seconds
    [2018-01-06 16:34:41] thread 4: 91742 hashes, 1.58 khash/s[/i]

    It stayed up for about 7 minutes and then starting having Stratum connection issues again!?  *sigh*

    That's either your network connection (not the miner), the pool, or some router in the middle. Try a different pool to see if you get the same results.

  • realbagdad
    Newbie
    *
    Offline Offline

    Activity: 39
    Merit: 0


    View Profile
    January 06, 2018, 03:47:44 AM
     #21828
    Quote from: buckonz on January 06, 2018, 02:28:45 AM
    Quote from: starcrys on January 06, 2018, 02:17:55 AM
    Erm...Can anyone help me on enabling staking? I've put "staking=1" and "posii=1" (with out the " ") in the magi.conf but the wallet still shows not staking (only those 2 commands were input)... Can someone help me on where I've gone wrong? Thanks.

    Have you specifically unlocked your wallet for staking?

    magid walletpassphrase YOUR_PASSWORD 9999999 true

    Is this a necessary step beyond getting the icon lit up in the Wallet GUI?

  • ParaplegicRacehorse
    Member
    **
    Offline Offline

    Activity: 79
    Merit: 36

    HODL. Patience.


    View Profile
    January 06, 2018, 03:59:20 AM
     #21829
    Quote from: realbagdad on January 06, 2018, 03:47:44 AM
    Quote
    magid walletpassphrase YOUR_PASSWORD 9999999 true

    Is this a necessary step beyond getting the icon lit up in the Wallet GUI?

    If you have the little miner tools lit up, you're minting. If you're in gui and the tools are not lit up, you can use the Mint menu. Else that cli command, above, will work.

  • jjude80
    Newbie
    *
    Offline Offline

    Activity: 48
    Merit: 0


    View Profile
    January 06, 2018, 04:06:37 AM
     #21830
    We are there, getting rejected blocks still though....

  • 111magic
    Legendary
    *
    Offline Offline

    Activity: 1764
    Merit: 1005



    View Profile
    January 06, 2018, 04:07:54 AM
     #21831
    Last block!! 🙈
    bitcoin: bc1qyadvvyv29z08ln2ta7g3uqwzkscr7wq4p09wuz

  • trader03
    Newbie
    *
    Offline Offline

    Activity: 56
    Merit: 0


    View Profile
    January 06, 2018, 04:15:26 AM
     #21832
    Historical moment friends we are in block 1606950 woooowwwwww HAPPY NEW MINING ROUND  Grin  Grin

    Thank you God, I woke up just in time to witness the moment

  • mkropinack
    Newbie
    *
    Offline Offline

    Activity: 5
    Merit: 0


    View Profile
    January 06, 2018, 04:17:14 AM
     #21833
    Correct me if I'm wrong, but I took a look at the change history for the code and based on what I know about the attack, we shouldn't be seeing the next block for another 1 hour and 55 minutes.

    Since the window was changed from 2 hours to 5 minutes, I think that we need to wait for wallclock time to catch up to the last block (#1606949), which I guess is about 2 hours into the future.

    Also, based on the 10 minute wait time between mined blocks, it would actually be 2 hours, 5 minutes.

    -MK
    (for a python coder, I've been reading way too much C lately)

  • jjude80
    Newbie
    *
    Offline Offline

    Activity: 48
    Merit: 0


    View Profile
    January 06, 2018, 04:21:21 AM
     #21834
    Quote from: mkropinack on January 06, 2018, 04:17:14 AM
    Correct me if I'm wrong, but I took a look at the change history for the code and based on what I know about the attack, we shouldn't be seeing the next block for another 1 hour and 55 minutes.

    Since the window was changed from 2 hours to 5 minutes, I think that we need to wait for wallclock time to catch up to the last block (#1606949), which I guess is about 2 hours into the future.

    Also, based on the 10 minute wait time between mined blocks, it would actually be 2 hours, 5 minutes.

    -MK
    (for a python coder, I've been reading way too much C lately)
    Sound theory. Anyone verify this claim?

  • stevr59
    Newbie
    *
    Offline Offline

    Activity: 21
    Merit: 0


    View Profile WWW
    January 06, 2018, 04:23:59 AM
     #21835
    Quote from: trader03 on January 06, 2018, 04:15:26 AM
    Historical moment friends we are in block 1606950 woooowwwwww HAPPY NEW MINING ROUND  Grin  Grin

    Thank you God, I woke up just in time to witness the moment

    [2018-01-05 22:22:19] Stratum connection interrupted
    [2018-01-05 22:22:49] Stratum connection failed: Connection timed out after 30000 milliseconds
    [2018-01-05 22:22:49] ...retry after 30 seconds

  • mkropinack
    Newbie
    *
    Offline Offline

    Activity: 5
    Merit: 0


    View Profile
    January 06, 2018, 04:29:00 AM
     #21836
    Quote from: jjude80 on January 06, 2018, 04:21:21 AM
    Quote from: mkropinack on January 06, 2018, 04:17:14 AM
    Correct me if I'm wrong, but I took a look at the change history for the code and based on what I know about the attack, we shouldn't be seeing the next block for another 1 hour and 55 minutes.

    Since the window was changed from 2 hours to 5 minutes, I think that we need to wait for wallclock time to catch up to the last block (#1606949), which I guess is about 2 hours into the future.

    Also, based on the 10 minute wait time between mined blocks, it would actually be 2 hours, 5 minutes.

    -MK
    (for a python coder, I've been reading way too much C lately)
    Sound theory. Anyone verify this claim?

    I just restarted my wallet (the new version).  It caught up to 1606949, and is stuck there.  I do see in my debug.log that some older wallets are publishing later blocks.  I suspect that those are the blocks that will be orphaned when the timer runs out?

    -MK

  • mkropinack
    Newbie
    *
    Offline Offline

    Activity: 5
    Merit: 0


    View Profile
    January 06, 2018, 04:36:48 AM
     #21837
    Quote from: mkropinack on January 06, 2018, 04:29:00 AM
    Quote from: jjude80 on January 06, 2018, 04:21:21 AM
    Quote from: mkropinack on January 06, 2018, 04:17:14 AM
    Correct me if I'm wrong, but I took a look at the change history for the code and based on what I know about the attack, we shouldn't be seeing the next block for another 1 hour and 55 minutes.

    Since the window was changed from 2 hours to 5 minutes, I think that we need to wait for wallclock time to catch up to the last block (#1606949), which I guess is about 2 hours into the future.

    Also, based on the 10 minute wait time between mined blocks, it would actually be 2 hours, 5 minutes.

    -MK
    (for a python coder, I've been reading way too much C lately)
    Sound theory. Anyone verify this claim?

    I just restarted my wallet (the new version).  It caught up to 1606949, and is stuck there.  I do see in my debug.log that some older wallets are publishing later blocks.  I suspect that those are the blocks that will be orphaned when the timer runs out?

    -MK

    >>> received block 0000051b7adc750dc706
    >>> Block 1606950 BlockTime=1515215660 CurrTime=1515213147 AdjustedTime=1515213146 vtx[0].nTime=1515215656
    >>> ERROR: AcceptBlock() : chain switch point reached
    >>> ERROR: ProcessBlock() : AcceptBlock FAILED
    >>> Misbehaving: 67.245.37.95:45844 (0 -> 100) DISCONNECTING

  • jjude80
    Newbie
    *
    Offline Offline

    Activity: 48
    Merit: 0


    View Profile
    January 06, 2018, 04:37:47 AM
     #21838
    Quote from: mkropinack on January 06, 2018, 04:29:00 AM
    Quote from: jjude80 on January 06, 2018, 04:21:21 AM
    Quote from: mkropinack on January 06, 2018, 04:17:14 AM
    Correct me if I'm wrong, but I took a look at the change history for the code and based on what I know about the attack, we shouldn't be seeing the next block for another 1 hour and 55 minutes.

    Since the window was changed from 2 hours to 5 minutes, I think that we need to wait for wallclock time to catch up to the last block (#1606949), which I guess is about 2 hours into the future.

    Also, based on the 10 minute wait time between mined blocks, it would actually be 2 hours, 5 minutes.

    -MK
    (for a python coder, I've been reading way too much C lately)
    Sound theory. Anyone verify this claim?

    I just restarted my wallet (the new version).  It caught up to 1606949, and is stuck there.  I do see in my debug.log that some older wallets are publishing later blocks.  I suspect that those are the blocks that will be orphaned when the timer runs out?

    -MK

    Evertime Im getting the following error the offset is getting lower. think we are in fact waiting for it to reach 0, its actually dropping really fast
    23:35:38: ntime warning: value 1515214991 (5a50588f) offset -1653 secs from uid 131

  • jonathin.r
    Member
    **
    Offline Offline

    Activity: 98
    Merit: 11


    View Profile
    January 06, 2018, 04:39:36 AM
     #21839
    Quote from: buckonz on January 06, 2018, 03:39:37 AM
    Quote from: s0litaire on January 06, 2018, 03:22:44 AM
    You can use it from there. but you might need to use the full path if you are going to use it in scripts:
    ~/m-cpuminer-v2/m-minerd <arguments>

    I ended up using the 'sudo make install' so now I can essentially run it from anywhere. I managed to get it going. However as I mentioned in a recent post, it struggles to maintain a connection to the BULL MINING pool.

    [2018-01-06 16:17:52] thread 6: 26396 hashes, 1.66 khash/s
    [2018-01-06 16:18:22] Stratum connection failed: Connection timed out after 30000 milliseconds

    ...and it didn't connect again until...

    [2018-01-06 16:32:43] ...retry after 30 seconds
    [2018-01-06 16:34:41] thread 4: 91742 hashes, 1.58 khash/s

    It stayed up for about 7 minutes and then starting having Stratum connection issues again!?  *sigh*

    Interestingly enough, both my miners, that have worked with other pools in the past, are having issues getting work from the BullMining pool. They may be having issues. When it looks like they got some work, I get a `Stratum connection failed: Connection timed out after 30001 milliseconds` error message.
    My XMG Address: 9LzxHqsxrRPMCyBffjMc3cLuB5hwEG5Ufq
    "Un pour tous, tous pour un" - The Three Musketeers, 1844

  • trader03
    Newbie
    *
    Offline Offline

    Activity: 56
    Merit: 0


    View Profile
    January 06, 2018, 04:44:20 AM
     #21840
    WAIT FRIENDS, PATIENCE Grin
    Pages: « 1 ... 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 [1092] 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 ... 1310 »
      Print  
Page 1091
Viewing Page: 1092

IRLBTC™ © 2025 IRLBTC.com