STAR COIN [STR] - The coin with bonus STAR blocks - page 35.

infinitevs

newbie

Activity: 42

Merit: 0

Thanks to all who bothered to try and help... Starcoin is pretty much dead as far as I can tell, removed from all exchanges and coinwarz :/

To the admin, you could have saved it... it may be too late now...

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: swiftshoot on October 21, 2013, 07:06:27 PM

Quote from: NorbyTheGeek on October 21, 2013, 10:58:45 AM

My understanding is that the "inbound" field refers to whether or not the peer connected to you, or the other way around:

inbound: false (My client initiated the connection to the peer)
inbound: true (The peer initiated the connection to me)

I don't think it has anything to do with whether or not a peer is sharing blocks. All peers should be sharing blocks unless there's a problem.

Of course, if I'm totally mistaken someone should set me straight. Wink

Theoretically that is how I understood it as well but in practice, it does not seem like so. When I opened up the ports to listen, poof I was able to sync correctly thereafter.

I've experienced the same with another *coind I'd just compiled - not a single block was offered until I figured out how to properly proxy inbound connects a couple of days later. My client was making plenty of outbound connect attempts during that time, including to specific addnode IPs suggested in the coin thread. I'm assuming that I was being blocked by peers for some reason, perhaps because they couldn't connect back to me? But I guess my IP stayed in peers.dat, so once they were able to connect inbound it all started flowing...

sheinsha

sr. member

Activity: 434

Merit: 250

The pool is mining fine, and getting nice block rate, just point your miners at str.minar.cc
No warning on pool client..

frobley

hero member

Activity: 708

Merit: 500

Quote from: infinitevs on October 29, 2013, 05:25:19 AM

Quote from: swiftshoot on October 28, 2013, 06:49:18 PM

Or the Dev can ignore our requests and make Starcoin go to "junk" status...

what a joke Sad

on another shitier note, for the last few days or so I have been receiving an error...

"errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers."

As well as trouble mining today, has anyone else had trouble solo mining today?

It keeps connecting then detecting a new block then goes back to waiting for work from the pool message???

Mining at Minar.cc seems to still be working fine which is very weird..

[EDIT] Solo Mining working fine again, though before when it wasn't I tried it on 3 seperate clients and was having the same issue Sad

[/edit]

I had the checkpoint warning, must have been same time; I did again the fix someone posted, downloaded fresh blockchain, then move wallet.dat into it, warning was gone then

infinitevs

newbie

Activity: 42

Merit: 0

Quote from: swiftshoot on October 28, 2013, 06:49:18 PM

Or the Dev can ignore our requests and make Starcoin go to "junk" status...

what a joke Sad

on another shitier note, for the last few days or so I have been receiving an error...

"errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers."

As well as trouble mining today, has anyone else had trouble solo mining today?

It keeps connecting then detecting a new block then goes back to waiting for work from the pool message???

Mining at Minar.cc seems to still be working fine which is very weird..

[EDIT] Solo Mining working fine again, though before when it wasn't I tried it on 3 seperate clients and was having the same issue Sad

[/edit]

ethought

legendary

Activity: 1316

Merit: 1000

Have re-enabled Starcoin pool on https://www.miningpool.co

Let me know if there are any problems.

Happy mining!

swiftshoot

full member

Activity: 200

Merit: 100

Or the Dev can ignore our requests and make Starcoin go to "junk" status...

swiftshoot

full member

Activity: 200

Merit: 100

Quote from: NorbyTheGeek on October 21, 2013, 10:58:45 AM

Quote from: swiftshoot on October 20, 2013, 08:11:15 PM

do a getpeerinfo
are all your peers have
"inbound" : false,
or any of them
"inbound" : true,

If they are all false, then you are on a different blockchain.
I have 11 of 18 connections that are set to true.

My understanding is that the "inbound" field refers to whether or not the peer connected to you, or the other way around:

inbound: false (My client initiated the connection to the peer)
inbound: true (The peer initiated the connection to me)

I don't think it has anything to do with whether or not a peer is sharing blocks. All peers should be sharing blocks unless there's a problem.

Of course, if I'm totally mistaken someone should set me straight. Wink

Theoretically that is how I understood it as well but in practice, it does not seem like so. When I opened up the ports to listen, poof I was able to sync correctly thereafter.

Maybe the Dev can shed some light on this issue?

swiftshoot

full member

Activity: 200

Merit: 100

Quote from: infinitevs on October 20, 2013, 10:28:37 PM

Hi Swiftshoot,

Properly read what I wrote...

...
-maxreceivebuffer= Maximum per-connection receive buffer, *1000 bytes (default: 5000)
-maxsendbuffer= Maximum per-connection send buffer, *1000 bytes (default: 1000)
-upnp Use UPnP to map the listening port (default: 0)
-detachdb Detach block and address databases. Increases shutdown time (default: 0)
-paytxfee= Fee per KB to add to transactions you send
...

Yes I did see it. Just mentioning that the Windows GUI version did not mention the -upnp option as in the help menu. It should be updated to have the same options as the starcoind.exe is all I am saying.

NorbyTheGeek

full member

Activity: 201

Merit: 100

Quote from: swiftshoot on October 20, 2013, 08:11:15 PM

do a getpeerinfo
are all your peers have
"inbound" : false,
or any of them
"inbound" : true,

If they are all false, then you are on a different blockchain.
I have 11 of 18 connections that are set to true.

My understanding is that the "inbound" field refers to whether or not the peer connected to you, or the other way around:

inbound: false (My client initiated the connection to the peer)
inbound: true (The peer initiated the connection to me)

I don't think it has anything to do with whether or not a peer is sharing blocks. All peers should be sharing blocks unless there's a problem.

Of course, if I'm totally mistaken someone should set me straight. Wink

swordfish6975

hero member

Activity: 721

Merit: 523

Quote from: pr0d1gy on October 21, 2013, 01:50:17 AM

Is this coin ever coming back to cryptsy?

that's what I would like to know Cheesy

pr0d1gy

hero member

Activity: 658

Merit: 502

Is this coin ever coming back to cryptsy?

infinitevs

newbie

Activity: 42

Merit: 0

Hi Swiftshoot,

Properly read what I wrote...

C:\Users\infinitevs\Desktop\starcoin>starcoind /?
StarCoin version v1.5.0.0

Usage:
StarCoind [options]
StarCoind [options] [params] Send command to -server or StarCoind
StarCoind [options] help List commands
StarCoind [options] help Get help for a command

Options:
-? This help message
-conf= Specify configuration file (default: StarCoin.conf)
-pid= Specify pid file (default: StarCoind.pid)
-gen Generate coins
-gen=0 Don't generate coins
-datadir= Specify data directory
-dbcache= Set database cache size in megabytes (default: 25)
-dblogsize= Set database disk log size in megabytes (default: 100)
-timeout= Specify connection timeout in milliseconds (default: 5000)
-proxy= Connect through socks proxy
-socks= Select the version of socks proxy to use (4-5, default: 5)
-tor= Use proxy to reach tor hidden services (default: same as -proxy)
-dns Allow DNS lookups for -addnode, -seednode and -connect
-port= Listen for connections on (default: 18216 or testnet: 28216)
-maxconnections= Maintain at most connections to peers (default: 125)
-addnode= Add a node to connect to and attempt to keep the connection open
-connect= Connect only to the specified node(s)
-seednode= Connect to a node to retrieve peer addresses, and disconnect
-externalip= Specify your own public address
-onlynet= Only connect to nodes in network (IPv4, IPv6 or Tor)
-discover Discover own IP address (default: 1 when listening and no -externalip)
-irc Find peers using internet relay chat (default: 1)
-listen Accept connections from outside (default: 1 if no -proxy or -connect)
-bind= Bind to given address. Use [host]:port notation for IPv6
-dnsseed Find peers using DNS lookup (default: 0)
-nosynccheckpoints Disable sync checkpoints (default: 0)
-banscore= Threshold for disconnecting misbehaving peers (default: 100)
-bantime= Number of seconds to keep misbehaving peers from reconnecting (default: 86400)
-maxreceivebuffer= Maximum per-connection receive buffer, *1000 bytes (default: 5000)
-maxsendbuffer= Maximum per-connection send buffer, *1000 bytes (default: 1000)
-upnp Use UPnP to map the listening port (default: 0)
-detachdb Detach block and address databases. Increases shutdown time (default: 0)
-paytxfee= Fee per KB to add to transactions you send
-testnet Use the test network
-debug Output extra debugging information. Implies all other -debug* options
-debugnet Output extra network debugging information
-logtimestamps Prepend debug output with timestamp
-shrinkdebugfile Shrink debug.log file on client startup (default: 1 when no -debug)
-printtoconsole Send trace/debug info to console instead of debug.log file
-printtodebugger Send trace/debug info to debugger
-rpcuser= Username for JSON-RPC connections
-rpcpassword= Password for JSON-RPC connections
-rpcport= Listen for JSON-RPC connections on (default: 18217 or testnet: 28217)
-rpcallowip= Allow JSON-RPC connections from specified IP address
-rpcconnect= Send commands to node running on (default: 127.0.0.1)
-blocknotify= Execute command when the best block changes (%s in cmd is replaced by block hash)
-upgradewallet Upgrade wallet to latest format
-keypool= Set key pool size to (default: 100)
-rescan Rescan the block chain for missing wallet transactions
-salvagewallet Attempt to recover private keys from a corrupt wallet.dat
-checkblocks= How many blocks to check at startup (default: 2500, 0 = all)
-checklevel= How thorough the block verification is (0-6, default: 1)
-loadblock= Imports blocks from external blk000?.dat file

Block creation options:
-blockminsize= Set minimum block size in bytes (default: 0)
-blockmaxsize= Set maximum block size in bytes (default: 250000)
-blockprioritysize= Set maximum size of high-priority/low-fee transactions in bytes (default: 27000)

SSL options: (see the Bitcoin Wiki for SSL setup instructions)
-rpcssl Use OpenSSL (https) for JSON-RPC connections
-rpcsslcertificatechainfile= Server certificate file (default: server.cert)
-rpcsslprivatekeyfile= Server private key (default: server.pem)
-rpcsslciphers= Acceptable ciphers (default: TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH)

swiftshoot

full member

Activity: 200

Merit: 100

Quote from: infinitevs on October 20, 2013, 09:55:04 PM

Hi Swiftshoot,

close starcoin-qt and backup and delete peers.dat in your data directory.. update the starcoin.conf with something similar to the below config

Code:

daemon=1
bind=192.168.0.x
port=18216
listen=1
maxconnections=8
logtimestamps=1
gen=0
splash=0
dns=1
discover=1
irc=0
dnsseed=0
#onlynet=IPv4
server=1
rpcuser=x
rpcpassword=x
rpcport=18217
rpcallowip=192.168.0.x
rpcallowip=192.168.0.x
rpcallowip=192.168.0.x
rpcallowip=192.168.0.x
rpcconnect=192.168.0.x
#seednode=add-any-other-known-bad-ips-then-uncomment
connect=37.229.117.57
connect=63.246.129.56:36302
connect=82.9.77.178
connect=198.84.250.234
connect=212.119.171.18
connect=216.155.151.242

start starcoin-qt

hope it helps..

also before you mentioned that the client had no upnp support, well the starcoind does... to get it setup automatically close starcoin-qt, then in a command prompt in windows type :

starcoind -upnp

now wait it will take a while to load and not say anything.. leave that prompt open and open another.. in this prompt keep trying:

starcoind getinfo

until you get a response that isn't server not found, once you get a response

you can close both the command prompts, UPNP for that client has been set in the router!

Here are Starcoin's command line options.. no option for -upnp. Not sure if it is in the source but I will check.
**Update: Checked source... it was defaulted to USE_UPNP=0 when compiled and therefore reason why it was not visible. For next version could you please ensure it is compiled with USE_UPNP=1 so that it will automatically work for Windows.

Options:
  -? This help message
  -conf= Specify configuration file (default: StarCoin.conf)
  -pid= Specify pid file (default: StarCoind.pid)
  -gen Generate coins
  -gen=0 Don't generate coins
  -datadir= Specify data directory
  -dbcache= Set database cache size in megabytes (default: 25)
  -dblogsize= Set database disk log size in megabytes (default: 100)
  -timeout= Specify connection timeout in milliseconds (default: 5000)
  -proxy= Connect through socks proxy
  -socks= Select the version of socks proxy to use (4-5, default: 5)
  -tor= Use proxy to reach tor hidden services (default: same as -proxy)
  -dns Allow DNS lookups for -addnode, -seednode and -connect
  -port= Listen for connections on (default: 18216 or testnet: 28216)
  -maxconnections= Maintain at most connections to peers (default: 125)
  -addnode= Add a node to connect to and attempt to keep the connection open
  -connect= Connect only to the specified node(s)
  -seednode= Connect to a node to retrieve peer addresses, and disconnect
  -externalip= Specify your own public address
  -onlynet= Only connect to nodes in network (IPv4, IPv6 or Tor)
  -discover Discover own IP address (default: 1 when listening and no -externalip)
  -irc Find peers using internet relay chat (default: 1)
  -listen Accept connections from outside (default: 1 if no -proxy or -connect)
  -bind= Bind to given address. Use [host]:port notation for IPv6
  -dnsseed Find peers using DNS lookup (default: 0)
  -nosynccheckpoints Disable sync checkpoints (default: 0)
  -banscore= Threshold for disconnecting misbehaving peers (default: 100)
  -bantime= Number of seconds to keep misbehaving peers from reconnecting (default: 86400)
  -maxreceivebuffer= Maximum per-connection receive buffer, *1000 bytes (default: 5000)
  -maxsendbuffer= Maximum per-connection send buffer, *1000 bytes (default: 1000)
  -detachdb Detach block and address databases. Increases shutdown time (default: 0)
  -paytxfee= Fee per KB to add to transactions you send
  -server Accept command line and JSON-RPC commands
  -testnet Use the test network
  -debug Output extra debugging information. Implies all other -debug* options
  -debugnet Output extra network debugging information
  -logtimestamps Prepend debug output with timestamp
  -shrinkdebugfile Shrink debug.log file on client startup (default: 1 when no -debug)
  -printtoconsole Send trace/debug info to console instead of debug.log file
  -printtodebugger Send trace/debug info to debugger
  -rpcuser= Username for JSON-RPC connections
  -rpcpassword= Password for JSON-RPC connections
  -rpcport= Listen for JSON-RPC connections on (default: 18217 or testnet: 28217)
  -rpcallowip= Allow JSON-RPC connections from specified IP address
  -rpcconnect= Send commands to node running on (default: 127.0.0.1)
  -blocknotify= Execute command when the best block changes (%s in cmd is replaced by block hash)
  -upgradewallet Upgrade wallet to latest format
  -keypool= Set key pool size to (default: 100)
  -rescan Rescan the block chain for missing wallet transactions
  -salvagewallet Attempt to recover private keys from a corrupt wallet.dat
  -checkblocks= How many blocks to check at startup (default: 2500, 0 = all)
  -checklevel= How thorough the block verification is (0-6, default: 1)
  -loadblock= Imports blocks from external blk000?.dat file

Block creation options:
  -blockminsize= Set minimum block size in bytes (default: 0)
  -blockmaxsize= Set maximum block size in bytes (default: 250000)
  -blockprioritysize= Set maximum size of high-priority/low-fee transactions in bytes (default: 27000)

SSL options: (see the Bitcoin Wiki for SSL setup instructions)
  -rpcssl Use OpenSSL (https) for JSON-RPC connections
  -rpcsslcertificatechainfile= Server certificate file (default: server.cert)
  -rpcsslprivatekeyfile= Server private key (default: server.pem)
  -rpcsslciphers= Acceptable ciphers (default: TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH)

UI options:
  -lang= Set language, for example "de_DE" (default: system locale)
  -min Start minimized
  -splash Show splash screen on startup (default: 1)

infinitevs

newbie

Activity: 42

Merit: 0

Quote from: 794259332 on October 20, 2013, 09:57:05 PM

swordfish6975

hero member

Activity: 721

Merit: 523

is this coin still around, its not on cryptsy atm?

794259332

sr. member

Activity: 462

Merit: 251

infinitevs

newbie

Activity: 42

Merit: 0

Hi Swiftshoot,

close starcoin-qt and backup and delete peers.dat in your data directory.. update the starcoin.conf with something similar to the below config

Code:

daemon=1
bind=192.168.0.x
port=18216
listen=1
maxconnections=8
logtimestamps=1
gen=0
splash=0
dns=1
discover=1
irc=0
dnsseed=0
#onlynet=IPv4
server=1
rpcuser=x
rpcpassword=x
rpcport=18217
rpcallowip=192.168.0.x
rpcallowip=192.168.0.x
rpcallowip=192.168.0.x
rpcallowip=192.168.0.x
rpcconnect=192.168.0.x
#seednode=add-any-other-known-bad-ips-then-uncomment
connect=37.229.117.57
connect=63.246.129.56:36302
connect=82.9.77.178
connect=198.84.250.234
connect=212.119.171.18
connect=216.155.151.242

start starcoin-qt

hope it helps..

also before you mentioned that the client had no upnp support, well the starcoind does... to get it setup automatically close starcoin-qt, then in a command prompt in windows type :

starcoind -upnp

now wait it will take a while to load and not say anything.. leave that prompt open and open another.. in this prompt keep trying:

starcoind getinfo

until you get a response that isn't server not found, once you get a response

you can close both the command prompts, UPNP for that client has been set in the router!

swiftshoot

full member

Activity: 200

Merit: 100

Quote from: infinitevs on October 20, 2013, 03:06:48 PM

SO NOW WE ARE ALL GOOD - Completely in SYNC, AWESOME..

Also I have made some changes to the conf file that will force the client to sync off of the good clients that I have found for the time being to prevent this happening again from bad clients... If anyone needs a hand just give me a yell...

Kind of curious what did you do to change your starcoin.conf to weed out the bad clients...

swiftshoot

full member

Activity: 200

Merit: 100

Quote from: NorbyTheGeek on October 20, 2013, 10:01:14 AM

Quote from: swiftshoot on October 20, 2013, 08:23:46 AM

Ok found the listen=1 bug. Starcoin has no uPnP capability and therefore the ports don't get forwarded to your Router.
You will need to add an entry into your Router or uPnP settings within Windows to allow users to connect to you.

Are you sure? I'm running starcoin-qt on Windows 7 and have inbound connections, but I haven't configured anything special on my router.

do a getpeerinfo
are all your peers have
"inbound" : false,
or any of them
"inbound" : true,

If they are all false, then you are on a different blockchain.
I have 11 of 18 connections that are set to true.

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