Pages:
Author

Topic: CLOSED..... - page 21. (Read 123134 times)

sr. member
Activity: 309
Merit: 250
July 31, 2014, 12:03:08 PM
Good Morning!

Any news?
- Fry is Pulsing :3
(Exchange is still low, I guess nobody wants the coin :/)

- QB will start Pulse before the 12Million mark.
Can't tell you yet when because over half of the team is on vacation.

- Pulse version 0.1 is going to be released on this weekend adding a whole bunch of new and awesome stuff
(Fry currently runs 0.1-rc1, minimalistic code has been changed since 0.1-rc1, expect same behaviour)

----

Thanks for your response, yes I have tried switching rpc ports as they can be of any assignment, and have triple checked everything....still can't connect.....its probably best to stay with the P2pool anyhow, but really wanted to solve the problem seeing as I have encountered this with a few other wallets.....perhaps the actual wallet port number (31616) is no longer the same as it was prior to the wallet being repaired??
If you compiled your wallet from source I find I sometimes have problems if I don't specify not to use UPnP
Code:
USE_UPNP=-
for example, from your CinniCoin source code folder:
Code:
make -f makefile.unix USE_UPNP=-

I used Windows compilation...so......??

Hey SRBOOTH,

Ports havent changed. Compiling on Windows can be tricky but it's essentially the same commands that derrend posted you.
The wallets we provided should work fine for solomining though.

Can you post us what wallet-config, miner-software(+version) & the arguments you passed to the miner ?

Thanks!

---

BTW these kind of issues are best solved on the IRC because we can strikeout some answer-delays Wink

---

So much for the news!
Long post, I apologize ;P

- f0o

I'm using the following .... downloaded from OP link at github--     v0.8.6.0-g04854e1-crf-beta

rpcuser=USER
rpcpassword=PASSWORD
maxconnections=300
rpcallowip=127.0.0.1
rpcport=31515
port=31616
daemon=1
listen=1
server=1

                              ccminer35-50.exe -a quark -o 127.0.0.1:31515 -u USER -p PASSWORD

Mining works fine at P2pool...........Thanks for your reply
hero member
Activity: 728
Merit: 500
July 31, 2014, 09:42:08 AM
welcome back Obfuscode and Jonesd!  Smiley
legendary
Activity: 1876
Merit: 1014
July 31, 2014, 04:44:37 AM
Hey everybody!

I'm back from holidays! Time for new steps! Smiley
hero member
Activity: 707
Merit: 505
July 30, 2014, 04:52:49 AM
So much for the news!
Still loving the whole quarkbar experience so far Smiley Thanks for the update, looking forward to next week Cheesy
sr. member
Activity: 294
Merit: 250
July 30, 2014, 03:36:34 AM
Good Morning!

Any news?
- Fry is Pulsing :3
(Exchange is still low, I guess nobody wants the coin :/)

- QB will start Pulse before the 12Million mark.
Can't tell you yet when because over half of the team is on vacation.

- Pulse version 0.1 is going to be released on this weekend adding a whole bunch of new and awesome stuff
(Fry currently runs 0.1-rc1, minimalistic code has been changed since 0.1-rc1, expect same behaviour)

----

Thanks for your response, yes I have tried switching rpc ports as they can be of any assignment, and have triple checked everything....still can't connect.....its probably best to stay with the P2pool anyhow, but really wanted to solve the problem seeing as I have encountered this with a few other wallets.....perhaps the actual wallet port number (31616) is no longer the same as it was prior to the wallet being repaired??
If you compiled your wallet from source I find I sometimes have problems if I don't specify not to use UPnP
Code:
USE_UPNP=-
for example, from your CinniCoin source code folder:
Code:
make -f makefile.unix USE_UPNP=-

I used Windows compilation...so......??

Hey SRBOOTH,

Ports havent changed. Compiling on Windows can be tricky but it's essentially the same commands that derrend posted you.
The wallets we provided should work fine for solomining though.

Can you post us what wallet-config, miner-software(+version) & the arguments you passed to the miner ?

Thanks!

---

BTW these kind of issues are best solved on the IRC because we can strikeout some answer-delays Wink

---

So much for the news!
Long post, I apologize ;P

- f0o
hero member
Activity: 707
Merit: 505
July 27, 2014, 05:16:18 PM
Any news?
We're basically on pause until August so not long now Smiley
hero member
Activity: 531
Merit: 500
AMD | Mining | NVIDIA
July 27, 2014, 04:52:36 PM
Any news?
hero member
Activity: 707
Merit: 505
July 23, 2014, 06:31:41 PM
I used Windows compilation...so......??
I'm afraid my knowledge is limited only to unix, I know nothing of windows Sad
sr. member
Activity: 309
Merit: 250
July 23, 2014, 05:54:34 PM
Thanks for your response, yes I have tried switching rpc ports as they can be of any assignment, and have triple checked everything....still can't connect.....its probably best to stay with the P2pool anyhow, but really wanted to solve the problem seeing as I have encountered this with a few other wallets.....perhaps the actual wallet port number (31616) is no longer the same as it was prior to the wallet being repaired??
If you compiled your wallet from source I find I sometimes have problems if I don't specify not to use UPnP
Code:
USE_UPNP=-
for example, from your CinniCoin source code folder:
Code:
make -f makefile.unix USE_UPNP=-

I used Windows compilation...so......??
hero member
Activity: 707
Merit: 505
July 23, 2014, 05:34:27 PM
Thanks for your response, yes I have tried switching rpc ports as they can be of any assignment, and have triple checked everything....still can't connect.....its probably best to stay with the P2pool anyhow, but really wanted to solve the problem seeing as I have encountered this with a few other wallets.....perhaps the actual wallet port number (31616) is no longer the same as it was prior to the wallet being repaired??
If you compiled your wallet from source I find I sometimes have problems if I don't specify not to use UPnP
Code:
USE_UPNP=-
for example, from your CinniCoin source code folder:
Code:
make -f makefile.unix USE_UPNP=-
sr. member
Activity: 309
Merit: 250
July 23, 2014, 11:51:34 AM
We're using bootstrap for frontend btw, so it's mobile friendly Smiley
I'm about to tackle bootstrap3 for a web app i'm writing in django, never used either of them before though so it's a learning curve.
May have to pic your brains later when I'm stuck.

I am unable to solo mine using previous OP settings of 31616 and 31615
P2P PORT:31616, RPC PORT:31515  ??

Thanks for pointing out the mistake , but still not working, strange. I have had this problem problem with a few wallets in the past, and successfully mined many others. Any other thoughts. Btw I made the conf changes and did restart the daemon.

It doesn't matter what port you use in the .conf file as long as it matches up to your miner config. Probably a case of missmatching data (user, password or ports) between the qb conf and the miner conf.

Thanks for your response, yes I have tried switching rpc ports as they can be of any assignment, and have triple checked everything....still can't connect.....its probably best to stay with the P2pool anyhow, but really wanted to solve the problem seeing as I have encountered this with a few other wallets.....perhaps the actual wallet port number (31616) is no longer the same as it was prior to the wallet being repaired??
hero member
Activity: 750
Merit: 500
July 23, 2014, 11:29:29 AM
We're using bootstrap for frontend btw, so it's mobile friendly Smiley
I'm about to tackle bootstrap3 for a web app i'm writing in django, never used either of them before though so it's a learning curve.
May have to pic your brains later when I'm stuck.

I am unable to solo mine using previous OP settings of 31616 and 31615
P2P PORT:31616, RPC PORT:31515  ??

Thanks for pointing out the mistake , but still not working, strange. I have had this problem problem with a few wallets in the past, and successfully mined many others. Any other thoughts. Btw I made the conf changes and did restart the daemon.

It doesn't matter what port you use in the .conf file as long as it matches up to your miner config. Probably a case of missmatching data (user, password or ports) between the qb conf and the miner conf.
sr. member
Activity: 309
Merit: 250
July 23, 2014, 11:19:31 AM
We're using bootstrap for frontend btw, so it's mobile friendly Smiley
I'm about to tackle bootstrap3 for a web app i'm writing in django, never used either of them before though so it's a learning curve.
May have to pic your brains later when I'm stuck.

I am unable to solo mine using previous OP settings of 31616 and 31615
P2P PORT:31616, RPC PORT:31515  ??

Thanks for pointing out the mistake , but still not working, strange. I have had this problem problem with a few wallets in the past, and successfully mined many others. Any other thoughts. Btw I made the conf changes and did restart the daemon.
zro
newbie
Activity: 56
Merit: 0
July 23, 2014, 04:56:34 AM
We're using bootstrap for frontend btw, so it's mobile friendly Smiley
I'm about to tackle bootstrap3 for a web app i'm writing in django, never used either of them before though so it's a learning curve.
May have to pic your brains later when I'm stuck.

Sure, no problem!
hero member
Activity: 707
Merit: 505
July 22, 2014, 07:43:58 PM
We're using bootstrap for frontend btw, so it's mobile friendly Smiley
I'm about to tackle bootstrap3 for a web app i'm writing in django, never used either of them before though so it's a learning curve.
May have to pic your brains later when I'm stuck.

I am unable to solo mine using previous OP settings of 31616 and 31615
P2P PORT:31616, RPC PORT:31515  ??
sr. member
Activity: 309
Merit: 250
July 22, 2014, 06:32:08 PM
Does anyone know the
port=
rpcport=

for the .conf file........I am unable to solo mine using previous OP settings of 31616 and 31615
thanks for the help
zro
newbie
Activity: 56
Merit: 0
July 22, 2014, 02:51:52 AM
Ofcourse, we are developing this from scratch, because we think it's easier to maintain and extend to our needs. We also have our own ideas for user security and would like to implement this ourselves.
There's not really a date for the market yet, but it's progressing bit by bit Smiley
I've no doubt it's going to be pink epic Smiley
Haha, we can make it pink ofcourse Wink

I want the layout to be friendly and somewhat bright... still looking on what's best.
If you guys have any ideas on colorschemes or good examples for a layout, let me know.

We're using bootstrap for frontend btw, so it's mobile friendly Smiley
hero member
Activity: 707
Merit: 505
July 21, 2014, 08:40:37 PM
Ofcourse, we are developing this from scratch, because we think it's easier to maintain and extend to our needs. We also have our own ideas for user security and would like to implement this ourselves.
There's not really a date for the market yet, but it's progressing bit by bit Smiley
I've no doubt it's going to be pink epic Smiley
zro
newbie
Activity: 56
Merit: 0
July 21, 2014, 07:25:33 AM
can you tell us anything about the market yet then zro?
are you building it using an existing open source project?
Ofcourse, we are developing this from scratch, because we think it's easier to maintain and extend to our needs. We also have our own ideas for user security and would like to implement this ourselves.
There's not really a date for the market yet, but it's progressing bit by bit Smiley
hero member
Activity: 728
Merit: 500
July 19, 2014, 06:43:38 AM
It's only a matter of weeks before this coin is worth $30 a piece. Rumor has it, Warren Buffet is interested and has been loading up on Quarkbar.
unlikely but the idea gives us something to talk about lol  Cheesy
Pages:
Jump to: