Pages:
Author

Topic: STAR COIN [STR] - The coin with bonus STAR blocks - page 13. (Read 143782 times)

member
Activity: 62
Merit: 10
Where can I find the windows wallet? I do not know how to build it.
I was solo mining this, but now I am stuck.  Thanks.
hero member
Activity: 574
Merit: 523
Is PoS been fixed with interest the same as before?  I still have some starcoin i've been keeping in a wallet since PoS broke last year.
Will I able to send and receive from crypsty if they havent updated?

The interest is the same. You will not be able to exchange with cryptsy until they update the wallet.
legendary
Activity: 1672
Merit: 1010
Is PoS been fixed with interest the same as before?  I still have some starcoin i've been keeping in a wallet since PoS broke last year.
Will I able to send and receive from crypsty if they havent updated?
hero member
Activity: 616
Merit: 500
If you're going to fix the problems, don't lower the pow:pos ratio like bee did. That changes the coin's original design entirely, and part of it's unique draw. Just fix the bugs.
newbie
Activity: 16
Merit: 0

Need some nodes, someone post


Here are all the peers I have @ V1.7
Code:
addnode=107.170.3.87
addnode=95.27.95.182
addnode=173.208.172.242
addnode=50.149.31.242
addnode=192.99.13.127
addnode=54.209.148.72
addnode=201.213.232.241
addnode=124.198.136.100
addnode=107.170.195.237
addnode=74.208.250.49
addnode=198.199.110.176

NOTICE

Just an update, I have been talking with bee7, veremit and sirnubbles about maintaining code/developing upon StarCoin further. We are working on implementing more secure features into StarCoin; right now you can expect an update by as soon as tonight. As bee7 stated previously he is not going to be a developer for this coin. He has also stated that he may submit pull requests if he sees fit. Currently I have synced version 1.7 with the stake lockup fix and I am actively mining blocks @ http://block.farm

I can confirm that bee7's fix has fixed the timewarp bug and corrected/fixed PoS.

I have also forked StarCoin and merged bee7's fixes @ https://github.com/strcoin/starcoin
All updates from the new dev team will be pushed to this repo ^^^^^^^^^^^^^^^^^^^

If you have any questions about the upcoming update stop by #starcoin @ http://webchat.freenode.net/
sr. member
Activity: 273
Merit: 250
Need some nodes, someone post
full member
Activity: 152
Merit: 100
Is there any ready made blockchain download? it will last forever to get in sync...
Or any already working pool?
full member
Activity: 182
Merit: 100
Compiling and testing now.  In the meantime, below is the section of code from the findblock cronjob that is generating the Proof of Stake messages for every block if this helps.  Looks to be detected by the flags property of the actual block.

Code:
     if ( ! empty($aBlockRPCInfo['flags']) && preg_match('/proof-of-stake/', $aBlockRPCInfo['flags']) ) {
        $log->logInfo("Block above with height " .  $aData['height'] . " not added to database, proof-of-stake block!");
        continue;
       }

The blocks you showed are actually PoS blocks. there is no way to make a PoS block with PoW mining - it will not pass the checks. I hope the fix I did solves the problem.

Don't appear to be finding anything now and we have 10 MH on it for 15 minutes.  Sad

Look like it may be an MPOS thing that i may have to work through.  Stratum miner seems to be reporting fine.  May look at bringing up a fresh instance of MPOS tonight with a new database and start from scratch with the new source.  Will keep you all posted.

To all miners mining on the pool, going to shutdown the stratum again until i figure things out so that you don't waste your has here.
hero member
Activity: 574
Merit: 523
Compiling and testing now.  In the meantime, below is the section of code from the findblock cronjob that is generating the Proof of Stake messages for every block if this helps.  Looks to be detected by the flags property of the actual block.

Code:
     if ( ! empty($aBlockRPCInfo['flags']) && preg_match('/proof-of-stake/', $aBlockRPCInfo['flags']) ) {
        $log->logInfo("Block above with height " .  $aData['height'] . " not added to database, proof-of-stake block!");
        continue;
       }

The blocks you showed are actually PoS blocks. there is no way to make a PoS block with PoW mining - it will not pass the checks. I hope the fix I did solves the problem.
full member
Activity: 182
Merit: 100
Compiling and testing now.  In the meantime, below is the section of code from the findblock cronjob that is generating the Proof of Stake messages for every block if this helps.  Looks to be detected by the flags property of the actual block.

Code:
     if ( ! empty($aBlockRPCInfo['flags']) && preg_match('/proof-of-stake/', $aBlockRPCInfo['flags']) ) {
        $log->logInfo("Block above with height " .  $aData['height'] . " not added to database, proof-of-stake block!");
        continue;
       }
hero member
Activity: 574
Merit: 523
full member
Activity: 182
Merit: 100
hero member
Activity: 574
Merit: 523
Seems when mining on the new source from our pool all we find are Proof of Stake blocks and no Proof of Work?  did you convert it to 100% PoS or is PoW still available?  Is it playing catch up from the PoS gap since January?  Should these be PoW and being detected incorrectly?

Code:
2014-05-23 11:17:46 - INFO --> Starting RPC block detecion, blocks are stored in Database
2014-05-23 11:17:46 - INFO --> | Blockhash            |          Height |     Amount | Confirmations |                Difficulty |               Time |
2014-05-23 11:17:46 - INFO --> | 68170c1442025a3ca... |          779000 |     100.03 |            25 |                0.00025978 | 2014-05-23 11:05:5 |
2014-05-23 11:17:46 - INFO --> Block above with height 779000 not added to database, proof-of-stake block!
2014-05-23 11:17:46 - INFO --> | 82995fbc99d9e0cbc... |          779004 |     100.03 |            21 |                0.00024414 | 2014-05-23 11:07:4 |
2014-05-23 11:17:46 - INFO --> Block above with height 779004 not added to database, proof-of-stake block!
2014-05-23 11:17:46 - INFO --> | c81259473ddd08f6c... |          779017 |     100.03 |             8 |                0.00024414 | 2014-05-23 11:12:3 |
2014-05-23 11:17:46 - INFO --> Block above with height 779017 not added to database, proof-of-stake block!
2014-05-23 11:17:46 - INFO --> | b7d7f694c785bc1ca... |          779003 |     100.03 |            22 |                0.00024414 | 2014-05-23 11:07:1 |
2014-05-23 11:17:46 - INFO --> Block above with height 779003 not added to database, proof-of-stake block!
2014-05-23 11:17:46 - INFO --> | 4b39d47a7bbb738ee... |          779022 |     100.02 |             3 |                0.00024414 | 2014-05-23 11:15:3 |
2014-05-23 11:17:46 - INFO --> Block above with height 779022 not added to database, proof-of-stake block!
2014-05-23 11:17:46 - INFO --> | 72ff66dfed947f748... |          779015 |     100.03 |            10 |                0.00024414 | 2014-05-23 11:11:0 |
2014-05-23 11:17:46 - INFO --> Block above with height 779015 not added to database, proof-of-stake block!
2014-05-23 11:17:46 - INFO --> | a5faf592c7a936dc7... |          779008 |     100.04 |            17 |                0.00024626 | 2014-05-23 11:08:2 |
2014-05-23 11:17:46 - INFO --> Block above with height 779008 not added to database, proof-of-stake block!

This is not your PoW mined block. It's a real PoS block:

Quote
starcoind getblock 68170c1442025a3ca9dd1eeb96ef1b3fb38516df1fbf5fc30e616b0fa3a465ec true
{
    "hash" : "68170c1442025a3ca9dd1eeb96ef1b3fb38516df1fbf5fc30e616b0fa3a465ec",
    "confirmations" : 197,
    "size" : 457,
    "height" : 779000,
    "version" : 4,
    "merkleroot" : "9ad23bae0f54036d57378d3b1fda27a14c11ec731cc68c9d21940d4015b5d43f",
    "mint" : 0.03000000,
    "time" : 1400857556,
    "nonce" : 0,
    "bits" : "1e0f095b",
    "difficulty" : 0.00025978,
    "previousblockhash" : "00000004b7fff57c17070b280229fb276ac63a64e1da22ab2ba49655997e4a9f",
    "nextblockhash" : "0000000c10b20b048f0017cd0185dec37bb3e65a98e3045149dc4a0dd4ac04bb",
    "flags" : "proof-of-stake",
    "proofhash" : "00088d1b45a1a63dca04aac2efb5b0d21c42708b2c4562fa394088379b12409d",
    "entropybit" : 0,
    "modifier" : "ddca04b0ab52d2ac",
    "modifierchecksum" : "ddb30b5f",
    "tx" : [
        {
            "txid" : "3a48eb06732a59e75a36c3d601c7ea4f7a40c7e18f4efe9b6119dad41db0155d",
            "txid" : "3a48eb06732a59e75a36c3d601c7ea4f7a40c7e18f4efe9b6119dad41db0155d",
            "version" : 2,
            "time" : 1400857556,
            "locktime" : 0,
            "vin" : [
                {
                    "coinbase" : "03f8e20b0112062f503253482f",
                    "sequence" : 4294967295
                }
            ],
            "vout" : [
                {
                    "value" : 0.00000000,
                    "n" : 0,
                    "scriptPubKey" : {
                        "asm" : "",
                        "hex" : "",
                        "type" : "nonstandard"
                    }
                }
            ]
        },
        {
            "txid" : "18ba8a719236df853e938eb59573a057cb19754908579b64bcfe7743bcc01256",
            "txid" : "18ba8a719236df853e938eb59573a057cb19754908579b64bcfe7743bcc01256",
            "version" : 2,
            "time" : 1400857556,
            "locktime" : 0,
            "vin" : [
                {
                    "txid" : "81dea1b3974e153b324648ca193d9013c509b8cfddcea8cadf34fb6c0f1e9936",
                    "vout" : 0,
                    "scriptSig" : {
                        "asm" : "304502205203af8db167d4f3216bad8b7c50f248b0fbab22773e3834c4fa923c2b0f4aad022100e e5fd2b176aa8d271cbe866b864d692cccf1a538e8ec5964d08fd081b6c4316601",
                        "hex" : "48304502205203af8db167d4f3216bad8b7c50f248b0fbab22773e3834c4fa923c2b0f4aad02210 0ee5fd2b176aa8d271cbe866b864d692cccf1a538e8ec5964d08fd081b6c4316601"
                    },
                    "sequence" : 4294967295
                }
            ],
            "vout" : [
                {
                    "value" : 0.00000000,
                    "n" : 0,
                    "scriptPubKey" : {
                        "asm" : "",
                        "hex" : "",
                        "type" : "nonstandard"
                    }
                },
                {
                    "value" : 50.01000000,
                    "n" : 1,
                    "scriptPubKey" : {
                        "asm" : "024ce1e1c26f10573057ebbb857471e2a1bc30b7a47dca5498a33b1333340229f9 OP_CHECKSIG",
                        "hex" : "21024ce1e1c26f10573057ebbb857471e2a1bc30b7a47dca5498a33b1333340229f9ac",
                        "reqSigs" : 1,
                        "type" : "pubkey",
                        "addresses" : [
                            "sReT5iKfCdAsgF32XtGGtz1V1xHGU4ZsDq"
                        ]
                    }
                },
                {
                    "value" : 50.02000000,
                    "n" : 2,
                    "scriptPubKey" : {
                        "asm" : "024ce1e1c26f10573057ebbb857471e2a1bc30b7a47dca5498a33b1333340229f9 OP_CHECKSIG",
                        "hex" : "21024ce1e1c26f10573057ebbb857471e2a1bc30b7a47dca5498a33b1333340229f9ac",
                        "reqSigs" : 1,
                        "type" : "pubkey",
                        "addresses" : [
                            "sReT5iKfCdAsgF32XtGGtz1V1xHGU4ZsDq"
                        ]
                    }
                }
            ]
        }
    ],
    "signature" : "304502203bcfd75a853b4abb9bfdefa83cad9498d4a3a760c1d342b87dff6bc2f7888c35022100b c3ef663832122fc8b0b38a743ac67a604a244a1dce40c0bc45594c981896288"
}

I suppose the "sReT5iKfCdAsgF32XtGGtz1V1xHGU4ZsDq" is the address in your wallet that was used for PoW mining.

So, we got a confirmation that the PoS is working. All your inputs that stayed long in a wallet are eligible for PoS, so they do their job! This is good.

Edit:

You could check the wallet's debug.log to find messages like "CPUMiner : proof-of-stake block found "

Edit2:
Do you really put some hashing power on? I have only 4 290x and it finds blocks quite regularly.

full member
Activity: 182
Merit: 100
Seems when mining on the new source from our pool all we find are Proof of Stake blocks and no Proof of Work?  did you convert it to 100% PoS or is PoW still available?  Is it playing catch up from the PoS gap since January?  Should these be PoW and being detected incorrectly?

IMPORTANT!!! - Stratum shutdown until issues defined below are resolved and the pool is working properly.  Will keep you posted.

Code:
2014-05-23 11:17:46 - INFO --> Starting RPC block detecion, blocks are stored in Database
2014-05-23 11:17:46 - INFO --> | Blockhash            |          Height |     Amount | Confirmations |                Difficulty |               Time |
2014-05-23 11:17:46 - INFO --> | 68170c1442025a3ca... |          779000 |     100.03 |            25 |                0.00025978 | 2014-05-23 11:05:5 |
2014-05-23 11:17:46 - INFO --> Block above with height 779000 not added to database, proof-of-stake block!
2014-05-23 11:17:46 - INFO --> | 82995fbc99d9e0cbc... |          779004 |     100.03 |            21 |                0.00024414 | 2014-05-23 11:07:4 |
2014-05-23 11:17:46 - INFO --> Block above with height 779004 not added to database, proof-of-stake block!
2014-05-23 11:17:46 - INFO --> | c81259473ddd08f6c... |          779017 |     100.03 |             8 |                0.00024414 | 2014-05-23 11:12:3 |
2014-05-23 11:17:46 - INFO --> Block above with height 779017 not added to database, proof-of-stake block!
2014-05-23 11:17:46 - INFO --> | b7d7f694c785bc1ca... |          779003 |     100.03 |            22 |                0.00024414 | 2014-05-23 11:07:1 |
2014-05-23 11:17:46 - INFO --> Block above with height 779003 not added to database, proof-of-stake block!
2014-05-23 11:17:46 - INFO --> | 4b39d47a7bbb738ee... |          779022 |     100.02 |             3 |                0.00024414 | 2014-05-23 11:15:3 |
2014-05-23 11:17:46 - INFO --> Block above with height 779022 not added to database, proof-of-stake block!
2014-05-23 11:17:46 - INFO --> | 72ff66dfed947f748... |          779015 |     100.03 |            10 |                0.00024414 | 2014-05-23 11:11:0 |
2014-05-23 11:17:46 - INFO --> Block above with height 779015 not added to database, proof-of-stake block!
2014-05-23 11:17:46 - INFO --> | a5faf592c7a936dc7... |          779008 |     100.04 |            17 |                0.00024626 | 2014-05-23 11:08:2 |
2014-05-23 11:17:46 - INFO --> Block above with height 779008 not added to database, proof-of-stake block!
full member
Activity: 201
Merit: 100
I've contacted Cryptsy and Coinwarz to let them know about the wallet update.
full member
Activity: 182
Merit: 100
We'll retract our message about closing the CharityMiningPools site for StarCoin with the recent developments.  Updating the source now and hopefully we can start hitting new blocks.  Will keep everyone posted as to when the updates are complete.

Big thanks to bee7 for taking the time to fix this up and get StarCoin up and running again.  This could be huge!
hero member
Activity: 574
Merit: 523
Generally speaking - no, you shouldn't, as the fork is at block 777856. It might be that all nodes your node is connected are running the old wallet.

Although I fixed the IRC seeding, try to add these nodes:

Code:
addnode=198.199.110.176
addnode=124.198.136.100
addnode=107.170.195.237
addnode=173.255.216.229
addnode=95.27.95.182

OK, thanks for that.
I'll replace the nodes and see what happens.

It should be fine as I already see at least one node that is completely synch'ed.
newbie
Activity: 9
Merit: 0
Generally speaking - no, you shouldn't, as the fork is at block 777856. It might be that all nodes your node is connected are running the old wallet.

Although I fixed the IRC seeding, try to add these nodes:

Code:
addnode=198.199.110.176
addnode=124.198.136.100
addnode=107.170.195.237
addnode=173.255.216.229
addnode=95.27.95.182

OK, thanks for that.
I'll replace the nodes and see what happens.
hero member
Activity: 574
Merit: 523
First and foremost, thanks to bee7 for getting this out .. myself and sirnubbles have been talking about a course of action .. but you're already ahead of us. Neither of us have sufficient knowledge of crypto wallets to push out an update quickly, and you've got something which, hopefully, will tide the community over. If you wish to stop by http://webchat.freenode.net/?channels=#starcoin would be good to meet and thank you in (digital) person.

I will visit it as it has web interface - I had no time yet to get familiar with standalone IRC client. As I mentioned there is a guy (girl) who is willing to maintain the code, but I did not ask for permission to publish the nick. I hope you will find each other.
newbie
Activity: 38
Merit: 0
First and foremost, thanks to bee7 for getting this out .. myself and sirnubbles have been talking about a course of action .. but you're already ahead of us. Neither of us have sufficient knowledge of crypto wallets to push out an update quickly, and you've got something which, hopefully, will tide the community over. If you wish to stop by http://webchat.freenode.net/?channels=#starcoin would be good to meet and thank you in (digital) person.

If anyone is able to come forward to help build a new team (or equally knows anyone), PLEASE stop by http://webchat.freenode.net/?channels=#starcoin or sirnubbles has a channel open on EFnet too. I cannot devote much time to move the coin forward, but as others have said .. it would be sad to see an otherwise good coin die.

NekoMiko - be patient.. there are only probably a handful of 'new' nodes available with any new blocks, if indeed any have been mined/minted yet.

Has anyone tweeted/msg'd cryptsy or anywhere else yet?

I shall be compiling bee7's source later on today, and hopefully will have another node running soon after. I will ensure sirnubbles gets his pool updated too (starcoin.mining.sexy), and we have been talking about getting the checkpoint node set up again .. this will probably roll into v1.7.1 or v1.8.

Thanks again to bee7 - and lets get this coin up and running once again!
Pages:
Jump to: