PoolServerJ - Tech Support

[Jine]

I'm still having serious issues with the db-connectivity.
Even with miners working against the poolserver, i get this issue.

Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: The last packet successfully received from the server was 8,777,967 milliseconds ago.  The last packet sent successfully to the server was 7,665,562 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.

[1714146960]

1714146960

[1714146960]

1714146960

[shads]

Does poolserverj have rollntime support?

It sort of does but not really... Meaning I half implemented it but never finished it.  It won't take much to finish but it will require a fairly extensive testing cycle afterwards.  I doubt it will ever support noncerange.  Supporting noncerange requires additional overhead for not much gain and with internal work generation about to be released which is orders of magnitude faster than json-rpc getwork, generating work is very cheap and unlikely to ever be a bottleneck again unless one day we have peta-hash pools.

[shads]

I'm still having serious issues with the db-connectivity.
Even with miners working against the poolserver, i get this issue.

Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: The last packet successfully received from the server was 8,777,967 milliseconds ago.  The last packet sent successfully to the server was 7,665,562 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.

I've only seen these sorts of issues twice before.  Onces was in a test setup where worker connection was unused for over 24 hours.  The other which looked a lot more like the quoted exception was using bulkloader engines but that was kind of a special case.  Using LOAD DATA INFILE statements with internal streams masqerading as the the LOCAL file. 

In any case I'm still a bit baffled.  The MySql class checks the state of the connection before using it.  i.e. if (conn.isClosed()) prepareConnection();  So this should only occur if the server is dropping the connection silently as far as I can tell and if it is then mysql is behaving pretty badly.  I will have a look at the code again today just to be sure though.

I notice in all these examples the time since last use is very high.  Do you have a miner running off the test pool constantly?  I wonder if that's the case if you're ever likely to see this in production?  Aside from the one example above which was a pretty unusual case I've never heard any reports of this happening in the field. 

[Jine]

Yes, i do have a miner working at ~6mh or something for testing. (A few shares per hour)
I'll point my 300mh miner against it as soon as i get home later tonight.

But still, pretty scary if this would happen in production - no shares are logged in db...
A hard restart of PSJ is required to get it up and running again.

Then it works for a few shares (at 6mh) and then it goes bad again.

[shads]

But still, pretty scary if this would happen in production - no shares are logged in db...
A hard restart of PSJ is required to get it up and running again.

True... I'm keen to find the source of it but as I said to my knowledge it's never happened in production.

BTW which version are you running?

[Jine]

0.3.0-FINAL, the binary version.

I'm struggling to compile from source, any walk-through or similar? Debian Squeeze, apt-get install maven2... then what?

EDIT:
Been playing around with mvn compile/install, installed all libs_non-mvn into my repo, but when i run "mvn compile" in poolserverj-core (which is a dependencie for poolserverj-core) i get this error:

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

/usr/src/bitcoin-poolserverj/poolserverj-core/src/main/java/com/shadworld/poolserver/entity/Worker.java:[70,16] generics are not supported in -source 1.3
(use -source 5 or higher to enable generics)
        private HashSet<String> allowedHosts = new HashSet();

/usr/src/bitcoin-poolserverj/poolserverj-core/src/main/java/com/shadworld/poolserver/entity/Worker.java:[77,17] for-each loops are not supported in -source 1.3
(use -source 5 or higher to enable for-each loops)
                        for (String h : allowedHosts) {

/usr/src/bitcoin-poolserverj/poolserverj-core/src/main/java/com/shadworld/poolserver/entity/UniquePortionString.java:[47,2] annotations are not supported in -source 1.3
(use -source 5 or higher to enable annotations)
        @Override

/usr/src/bitcoin-poolserverj/poolserverj-core/src/main/java/com/shadworld/poolserver/entity/FastEqualsSolution.java:[17,2] annotations are not supported in -source 1.3
(use -source 5 or higher to enable annotations)
        @Override

EDIT:
Installed poolserverj-core with mvn install:install-file, but I'm running into the same issue with compiling poolserverj-main :/

[shads]

Sorry I missed this post somehow... Your maven build is set to use java compliance level 1.3  I can't actually recall the setting but you need to declare the compliance level in the pom.xml file.

As an alternative I've just posted a guide to setting up the project in eclipse.  This is not for a maven setup but it's quickest easiest way to do it.  The only disadvantage is that you won't have attached source for some of the dependencies but unless it's very rare you need to go into those for debugging.

The guide is here:
http://poolserverj.org/documentation/guide-to-setting-up-poolserverj-in-eclipse-3-7/

If you set it up this way you'll be able to run poolserverj inside eclipse which will allow you to use all the debug features to follow what's going on.

[shads]

I'm still having serious issues with the db-connectivity.
Even with miners working against the poolserver, i get this issue.

Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: The last packet successfully received from the server was 8,777,967 milliseconds ago.  The last packet sent successfully to the server was 7,665,562 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.

just added handling on the worker db connection to catch connection exceptions and make an attempt to close and reopen connection.  Working on the shares connection now but that's a bit more involved.  I figure while I'm there I might as well deal with this feature request:
https://bitbucket.org/shadders/bitcoin-poolserverj/issue/10/failed-to-commit-to-database-should-cache

When connection fails start serializing shares to disk and recover them and start feeding to DB once connection state is normal again.

[shads]

Security HOTFIX - PLEASE UPDATE

see this post for details:
https://bitcointalk.org/index.php?topic=33142.msg608297#msg608297

[ThiagoCMC]

Hi!

 I just start the PoolServerJ 0.3.1 for the first time, I'm running it with litecoind.

 I got:

Code:

administrativo@ltcmining1:~/poolserverj-0.3.1/bin$ java -classpath poolserverj.jar:../lib/*:../lib/lib_non-maven/*:../lib/plugins com.shadworld.poolserver.servicelauncher.PoolServerService start ../conf-samples/local-daemon.properties 
Args - [2]: start ../conf-samples/local-daemon.properties 
PoolServerJ Service Starting Mon Nov 07 00:22:44 BRST 2011
[24:22:44.791] user.dir: /home/administrativo/poolserverj-0.3.1/bin
[24:22:44.792] Home path set to: /home/administrativo/poolserverj-0.3.1/bin/poolserverj.jar
[24:22:44.793] Home directory set from jar file location to: /home/administrativo/poolserverj-0.3.1
[24:22:44.818] Wrote PID: 22092 to pidFile: /home/administrativo/poolserverj-0.3.1/tmp/poolserverj.pid
[24:22:44.878] Connecting to DB URL: jdbc:mysql://localhost:3306/poolserverjdb?allowMultiQueries=true&zeroDateTimeBehavior=round&dumpQueriesOnException=true&dumpMetadataOnColumnNotFound=true&useCompression=true&autoReconnect=true
[24:22:45.174] Building Shares-DB-flush-engine: DefaultPreparedStatementSharesDBFlushEngine.class with extraParams: []
[24:22:45.175] Building Worker-authentication-engine: WorkerAuthenticator.class with extraParams: null
566 [main] INFO org.eclipse.jetty.util.log - jetty-7.4.0.v20110414
603 [main] INFO org.eclipse.jetty.util.log - started o.e.j.s.ServletContextHandler{/,null}
625 [main] INFO org.eclipse.jetty.util.log - Started SelectChannelConnector@0.0.0.0:8999 STARTING
626 [main] INFO org.eclipse.jetty.util.log - jetty-7.4.0.v20110414
626 [main] INFO org.eclipse.jetty.util.log - started o.e.j.s.ServletContextHandler{/,null}
629 [main] INFO org.eclipse.jetty.util.log - Started SelectChannelConnector@127.0.0.1:8997 STARTING
[24:22:45.372] Starting local work source proxy: bitcoind-patch
[24:22:45.373] PoolServerJ is open for business
[24:22:45.373] DaemonSource[bitcoind-patch] Native longpoll: false verification: true
[24:22:45.373] DaemonSource[bitcoind-patch] Native longpoll: false verification: true
[24:22:45.373] No native longpoll listeners registered, all sources will fall back to polling mode
PoolServerJ Service Started Mon Nov 07 00:22:45 BRST 2011
com.google.bitcoin.core.VerificationException: Difficulty target is bad: 43566378659636251172094964077388411969922914778514660462017772519424
	at com.google.bitcoin.core.Block.getDifficultyTargetAsInteger(Block.java:231)
	at com.shadworld.poolserver.BlockChainTracker.reportDifficultyTarget(BlockChainTracker.java:281)
	at com.shadworld.poolserver.source.WorkSource.cacheEntry(WorkSource.java:469)
	at com.shadworld.poolserver.source.WorkSource.processSingleWork(WorkSource.java:287)
	at com.shadworld.poolserver.source.daemonhandler.DaemonHandler.processSingleResponse(DaemonHandler.java:157)
	at com.shadworld.poolserver.source.daemonhandler.SingleWorkExchange.onResponseComplete(SingleWorkExchange.java:35)
	at org.eclipse.jetty.client.HttpExchange$Listener.onResponseComplete(HttpExchange.java:920)
	at org.eclipse.jetty.client.HttpEventListenerWrapper.onResponseComplete(HttpEventListenerWrapper.java:118)
	at org.eclipse.jetty.client.security.SecurityListener.onResponseComplete(SecurityListener.java:251)
	at org.eclipse.jetty.client.HttpExchange.setStatus(HttpExchange.java:263)
	at org.eclipse.jetty.client.HttpConnection$Handler.messageComplete(HttpConnection.java:622)
	at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:828)
	at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:220)
	at org.eclipse.jetty.client.HttpConnection.handle(HttpConnection.java:269)
	at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:515)
	at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:40)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:529)
	at java.lang.Thread.run(Thread.java:679)
com.google.bitcoin.core.VerificationException: Difficulty target is bad: 43566378659636251172094964077388411969922914778514660462017772519424
	at com.google.bitcoin.core.Block.getDifficultyTargetAsInteger(Block.java:231)
	at com.shadworld.poolserver.BlockChainTracker.reportDifficultyTarget(BlockChainTracker.java:281)
	at com.shadworld.poolserver.source.WorkSource.cacheEntry(WorkSource.java:469)
	at com.shadworld.poolserver.source.WorkSource.processSingleWork(WorkSource.java:287)
	at com.shadworld.poolserver.source.daemonhandler.DaemonHandler.processSingleResponse(DaemonHandler.java:157)
	at com.shadworld.poolserver.source.daemonhandler.SingleWorkExchange.onResponseComplete(SingleWorkExchange.java:35)
	at org.eclipse.jetty.client.HttpExchange$Listener.onResponseComplete(HttpExchange.java:920)
	at org.eclipse.jetty.client.HttpEventListenerWrapper.onResponseComplete(HttpEventListenerWrapper.java:118)
	at org.eclipse.jetty.client.security.SecurityListener.onResponseComplete(SecurityListener.java:251)
	at org.eclipse.jetty.client.HttpExchange.setStatus(HttpExchange.java:263)
	at org.eclipse.jetty.client.HttpConnection$Handler.messageComplete(HttpConnection.java:622)
	at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:828)
	at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:220)
	at org.eclipse.jetty.client.HttpConnection.handle(HttpConnection.java:269)
	at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:515)
	at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:40)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:529)
	at java.lang.Thread.run(Thread.java:679)
com.google.bitcoin.core.VerificationException: Difficulty target is bad: 43566378659636251172094964077388411969922914778514660462017772519424
	at com.google.bitcoin.core.Block.getDifficultyTargetAsInteger(Block.java:231)
	at com.shadworld.poolserver.BlockChainTracker.reportDifficultyTarget(BlockChainTracker.java:281)
	at com.shadworld.poolserver.source.WorkSource.cacheEntry(WorkSource.java:469)
	at com.shadworld.poolserver.source.WorkSource.processSingleWork(WorkSource.java:287)
	at com.shadworld.poolserver.source.daemonhandler.DaemonHandler.processSingleResponse(DaemonHandler.java:157)
	at com.shadworld.poolserver.source.daemonhandler.SingleWorkExchange.onResponseComplete(SingleWorkExchange.java:35)
	at org.eclipse.jetty.client.HttpExchange$Listener.onResponseComplete(HttpExchange.java:920)
	at org.eclipse.jetty.client.HttpEventListenerWrapper.onResponseComplete(HttpEventListenerWrapper.java:118)
	at org.eclipse.jetty.client.security.SecurityListener.onResponseComplete(SecurityListener.java:251)
	at org.eclipse.jetty.client.HttpExchange.setStatus(HttpExchange.java:263)
	at org.eclipse.jetty.client.HttpConnection$Handler.messageComplete(HttpConnection.java:622)
	at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:828)
	at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:220)
	at org.eclipse.jetty.client.HttpConnection.handle(HttpConnection.java:269)
	at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:515)
	at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:40)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:529)
	at java.lang.Thread.run(Thread.java:679)
com.google.bitcoin.core.VerificationException: Difficulty target is bad: 43566378659636251172094964077388411969922914778514660462017772519424

 This message: "com.google.bitcoin.core.VerificationException: Difficulty target is bad:" is expected?!

 And, how to enable LongPool?!

Thank you guys!
Thiago

[shads]

Well you're the first person to try it with litecoin to my knowledge...

0.3.1 is not SCrypt compatible.  You'll need the merged mining version.

Also I seem to recall there's something odd about litecoin difficulty?  Like it can be below 1 or something like that?

Can you post the results of a getwork from a litecoind here so I can see what the difficulty bits actually are?

[ThiagoCMC]

Good to know that I'm the first one!! lol

 Here we go:

Code:

administrativo@ltcmining1:~$ ./Litecoin/litecoin/src/litecoind getwork
{   
    "midstate" : "f2cfc038d83389f1e4e44eb67b4967f4e9c0352a9eb0cacb7cc01e04c84fa039",
    "data" : "00000001d8632caadf2260bf42d2067f60d987d6b790562b272653ae611ba0fa67fe1945e3c77cc0b144c2b408614956f4bdcff4ecf1c7f2818beb3e5c6cfd61083be20c4eb747fd1d019db000000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000",
    "hash1" : "00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000",
    "target" : "0000000000000000000000000000000000000000000000000000b09d01000000"
}

Code:

administrativo@ltcmining1:~$ ./Litecoin/litecoin/src/litecoind getdifficulty
0.61881515

 Thank you!

Best!
Thiago

[shads]

ok yes difficulty is below the minimum allowed.  I'll ask the dev what the minimum constant is and update PSJ.  There should be a major release later today or tomorrow so hopefull I'll get it included in that.

[ThiagoCMC]

WOW! Thank you!!

 I'm about to start my Litecoin pool, in portuguese for the brazillian people...

 Would love to use PoolServJ instead of PushPool...

Regards,
Thiago

[ThiagoCMC]

And about being SCrypt compatible?!
Maybe this can be a major problem?!

[Snapman]

WOW! Thank you!!

 I'm about to start my Litecoin pool, in portuguese for the brazillian people...

 Would love to use PoolServJ instead of PushPool...

Regards,
Thiago

I second that statemment, psj with scrypt compatibility would be extremely helpful for those of us who think "psj 0wnz pp in the face :O"

[Retard]

I would test to install PoolServerJ for merge mining but i have a problem and i dont know why ?

Namecoin Client running all Blocks Downloaded version 0.5
Bitcoin Client running all Blocks Downloaded version 0.5

Ubunut Version 10.11
PoolserverJ Version : poolserverj-0.4.0rc2
Mysql and all Daemons on the same server




but after start i get this

[03:18:03.560] Realm resolved null for key: localhost:8331/ Realm: jsonrpc
205349 [shared-httpclient-97] WARN org.eclipse.jetty.util.log - Unknown Security Realm: jsonrpc
[03:18:03.560] RETRY
[03:18:03.561] getblocknumber response status: 401 for url: http://localhost:8330/
[03:18:03.561] getblocknumber response status: 401 for url: http://localhost:8330/
[03:18:03.561] Realm resolved null for key: localhost:8331/ Realm: jsonrpc
205350 [shared-httpclient-229] WARN org.eclipse.jetty.util.log - Unknown Security Realm: jsonrpc
[03:18:03.562] RETRY
[03:18:03.562] Realm resolved null for key: localhost:8331/ Realm: jsonrpc
205351 [shared-httpclient-125] WARN org.eclipse.jetty.util.log - Unknown Security Realm: jsonrpc
[03:18:03.562] RETRY
[03:18:03.562] Realm resolved null for key: localhost:8331/ Realm: jsonrpc
205352 [shared-httpclient-82] WARN org.eclipse.jetty.util.log - Unknown Security Realm: jsonrpc
[03:18:03.563] RETRY
[03:18:03.563] getblocknumber response status: 401 for url: http://localhost:8330/
210667 [shared-httpclient-19] WARN org.eclipse.jetty.util.log - EXPIRED ContentExchange@1872384842=POST//localhost:8331/#8
[03:18:08.879] [WARN] Failed to build auxblock for chain: namecoin
java.lang.NullPointerException
   at com.shadworld.poolserver.source.merged.MergedMiningGroup.buildAuxBlock(MergedMiningGroup.java:262)
   at com.shadworld.poolserver.source.merged.MergedMiningGroup.updateAuxes(MergedMiningGroup.java:163)
   at com.shadworld.poolserver.Cleaner.run(Cleaner.java:54)
[03:18:08.879] [WARN] Reverting to rpc getauxblock for chain: namecoin
[03:18:33.480] getblocknumber response status: 401 for url: http://localhost:8330/
[03:18:33.485] Realm resolved null for key: localhost:8331/ Realm: jsonrpc
235274 [shared-httpclient-124] WARN org.eclipse.jetty.util.log - Unknown Security Realm: jsonrpc
[03:18:33.499] Realm resolved null for key: localhost:8331/ Realm: jsonrpc
235288 [shared-httpclient-70] WARN org.eclipse.jetty.util.log - Unknown Security Realm: jsonrpc

After start that checked all :

[03:45:31.932] Mapped parameter 1 to field 1 (remote_host)
[03:45:31.932] Mapped parameter 2 to field 2 (username)
[03:45:31.932] Mapped parameter 3 to field 3 (our_result)
[03:45:31.932] Mapped parameter 4 to field 4 (upstream_result)
[03:45:31.933] Mapped parameter 5 to field 5 (reason)
[03:45:31.933] Mapped parameter 6 to field 7 (time)
[03:45:31.933] Mapped parameter 7 to field 8 (source)
[03:45:31.933] Mapped parameter 8 to field 9 (block_num)
[03:45:31.933] Mapped parameter 9 to field 11 (useragent)
[03:45:31.935] Building Shares-DB-flush-engine: DefaultPreparedStatementSharesDBFlushEngine.class with extraParams: []
[03:45:31.936] Building Worker-authentication-engine: WorkerAuthenticator.class with extraParams: null
[03:45:31.979] Configuring aux daemon for WorkSource: bitcoind-mm
[03:45:31.979] Chain name: namecoin
[03:45:31.980] Chain id: 1
[03:45:31.980] Chain url: http://localhost:8331/
[03:45:31.980] Chain username: smart
[03:45:31.980] Chain payoutAddress: Mz3Qs4eDoE7USV8sjnCf8aATeHCJAtM5Zp
[03:45:31.980] Chain password: s***t
^C[03:45:32.343] Shutting down poolserver...
[03:45:32.343] Flushing cached shares...
[03:45:32.343] Flush shares cache complete...
[03:45:32.343] Waiting to complete upstream share submits...
[03:45:32.350] Finished upstream submits...
[03:45:32.350] Flushing final shares...
[03:45:32.365] 0 shares in 1,320,925,568 seconds. Current hashRate: 0 GH/s
[03:45:32.365] Submit Throttling on: false
[03:45:32.365] All share submits flushed...
[03:45:32.366] Waiting for threads to die...
[03:45:32.367] Dumping workmap to file: /home/smart/Downloads/poolserverj-0.4.0rc2/tmp/workmap-8332.bin
2449 [main] INFO org.eclipse.jetty.util.log - jetty-7.4.0.v20110414
2768 [main] INFO org.eclipse.jetty.util.log - started o.e.j.s.ServletContextHandler{/,null}
2869 [main] INFO org.eclipse.jetty.util.log - Started SelectChannelConnector@0.0.0.0:8332 STARTING
2873 [main] INFO org.eclipse.jetty.util.log - jetty-7.4.0.v20110414
2873 [main] INFO org.eclipse.jetty.util.log - started o.e.j.s.ServletContextHandler{/,null}
2907 [main] INFO org.eclipse.jetty.util.log - Started SelectChannelConnector@0.0.0.0:8997 STARTING
[03:45:32.919] Starting local work source proxy: bitcoind-mm

whats wrong ? any idea ?

i can need help to configure this -.- ....  pushpoold works without problems but i need a java version



best regards
Smart

[cablepair]

ok smart and I have that problem fixed by using the mini binary shads posted


Poolserverj is starting now

we are getting this message:

[06:07:45.255] Exception in Cleaner Thread
java.lang.NullPointerException
        at com.shadworld.poolserver.workmaker.WorkMaker.update(WorkMaker.java:178)
        at com.shadworld.poolserver.source.merged.MergedMiningGroup.updateAuxes(MergedMiningGroup.java:249)
        at com.shadworld.poolserver.Cleaner.run(Cleaner.java:54)


and miners cannot connect

although sometimes it will say "retriving worker from database"

any ideas?

[shads]

ok smart and I have that problem fixed by using the mini binary shads posted


Poolserverj is starting now

we are getting this message:

[06:07:45.255] Exception in Cleaner Thread
java.lang.NullPointerException
        at com.shadworld.poolserver.workmaker.WorkMaker.update(WorkMaker.java:178)
        at com.shadworld.poolserver.source.merged.MergedMiningGroup.updateAuxes(MergedMiningGroup.java:249)
        at com.shadworld.poolserver.Cleaner.run(Cleaner.java:54)


and miners cannot connect

although sometimes it will say "retriving worker from database"

any ideas?

see: https://bitcointalk.org/index.php?topic=51226.msg613256#msg613256

can people please keep tech support questions specific to the workmaker release in that thread...

I'm thinking I might close the other threads and link them all to that one to keep it simple.

[Remember remember the 5th of November]

What is the difference between 0.3.X and a Workmaker edition? Also, do i really need the 4diff patch? Cause i am using 0.3.24(I can upgrade if the problem is resolved) on windows, and it would be a pain in the ass to compile Bitcoin(with or without gui) on windows.