[ANN] [BTQ] BitQuark | Super secure hashing | CPU mining - page 20.

BitQuark

hero member

Activity: 716

Merit: 501

Quote from: ZeroFossilFuel on March 14, 2015, 08:00:07 AM

Quote from: BitQuark on February 11, 2015, 08:42:21 PM

Yeah that's the exact concern that I have. 20 block retargeting allows drop in miners to clean house and then leave smaller miners to pick up the pieces. As far as I know, there aren't any drawbacks to DGW3. If I can get everything up and going in time, I will release BTQ-r19 and have the DGW3 start at block 1,000,001.

Any news for this?

And IMHO, you probably won't see too much activity at Owler for two reasons. 1) The photo. Not exactly CEO material. 2) YASMSTWYT (Yet Another Social Media Site To Waste Your Time) that requires registration. I for one am on YASMSTWYT overload. My 2BTQ.

Haven't got the DGW3 added yet, but we are currently testing BitQuark Core 0.10 edition. So far everything is looking good!

I may also release a 64 bit client as well. I'll keep you guys posted!

ZeroFossilFuel

sr. member

Activity: 346

Merit: 250

Quote from: BitQuark on February 11, 2015, 08:42:21 PM

Yeah that's the exact concern that I have. 20 block retargeting allows drop in miners to clean house and then leave smaller miners to pick up the pieces. As far as I know, there aren't any drawbacks to DGW3. If I can get everything up and going in time, I will release BTQ-r19 and have the DGW3 start at block 1,000,001.

Any news for this?

And IMHO, you probably won't see too much activity at Owler for two reasons. 1) The photo. Not exactly CEO material. 2) YASMSTWYT (Yet Another Social Media Site To Waste Your Time) that requires registration. I for one am on YASMSTWYT overload. My 2BTQ.

BitQuark

hero member

Activity: 716

Merit: 501

Quote from: mkimid on February 19, 2015, 04:00:49 PM

Quote from: BitQuark on February 11, 2015, 08:42:21 PM

Quote from: CommanderVenus on February 11, 2015, 08:34:17 PM

Currently someone could jump on the network with a big hashrate and gobble up 20 blocks until the difficulty goes up and then leave the other miners to struggle with the higher difficulty. Wash rinse repeat. right?

It could be a wise decision. Any drawbacks though?

Yeah that's the exact concern that I have. 20 block retargeting allows drop in miners to clean house and then leave smaller miners to pick up the pieces. As far as I know, there aren't any drawbacks to DGW3. If I can get everything up and going in time, I will release BTQ-r19 and have the DGW3 start at block 1,000,001.

How about supporting some internal explorer and rebuild using btc core 0.10?

Addtionally
- memory pool list view for transaction
- latest block list usng blockindex map (block track information)

Just an idea,

If you know of anyone who is willing to transition BitQuark over to core 0.10, I will pay them 25,000 BTQ

BitQuark

hero member

Activity: 716

Merit: 501

Happy 1 Year to BitQuark!!!! Don't forget, if you're mining at http://www.WeMineBTQ.com and you find block 1,000,000 you will receive 10,000 BTQ's!!!!

mkimid

sr. member

Activity: 336

Merit: 250

Have A Nice Day

Quote from: Hilux74 on February 20, 2015, 12:41:34 PM

Quote from: BitQuark on February 12, 2015, 12:03:21 AM

ASIC coming soon for X-series algorithm coins!! This would also include Quark algorithm coin!

ASIC for X11, X13, X15 is very easy since they are a linear sequence of calculations, so regardless if 11, 13 or 15 rounds they always happen in the same sequence.

Quark algo has random hashing rounds so it is much harder to make an ASIC, not impossible but it would be much much more difficult than the X series algos so I do not believe it woud be included on ASIC hardware designed for X series. I'll believe it when I see it.

There is two type of design, modula or hardwire. I think, modula design will be better for the flexibility.
And, even in hardwire structure, Quark algo can be processed as whole types of algorithm. And just select the valid data in end stages. Such as

A - (B or C) - D

ASIC can designed to thru A - B (v) C (v) D
And, (v) will decide to use the pre-processed data or post-post processed data

But, to support multiple algorothim,
They designed common input matrix mux and output maxtrix mux with feed back bus,
And, control the mux and path using small logic
I think, not much complex,

just some algo has requipred too many gates that is only issues

Hilux74

legendary

Activity: 912

Merit: 1000

Quote from: BitQuark on February 12, 2015, 12:03:21 AM

ASIC coming soon for X-series algorithm coins!! This would also include Quark algorithm coin!

ASIC for X11, X13, X15 is very easy since they are a linear sequence of calculations, so regardless if 11, 13 or 15 rounds they always happen in the same sequence.

Quark algo has random hashing rounds so it is much harder to make an ASIC, not impossible but it would be much much more difficult than the X series algos so I do not believe it woud be included on ASIC hardware designed for X series. I'll believe it when I see it.

mkimid

sr. member

Activity: 336

Merit: 250

Have A Nice Day

Quote from: BitQuark on February 11, 2015, 08:42:21 PM

Quote from: CommanderVenus on February 11, 2015, 08:34:17 PM

Currently someone could jump on the network with a big hashrate and gobble up 20 blocks until the difficulty goes up and then leave the other miners to struggle with the higher difficulty. Wash rinse repeat. right?

It could be a wise decision. Any drawbacks though?

Yeah that's the exact concern that I have. 20 block retargeting allows drop in miners to clean house and then leave smaller miners to pick up the pieces. As far as I know, there aren't any drawbacks to DGW3. If I can get everything up and going in time, I will release BTQ-r19 and have the DGW3 start at block 1,000,001.

How about supporting some internal explorer and rebuild using btc core 0.10?

Addtionally
- memory pool list view for transaction
- latest block list usng blockindex map (block track information)

Just an idea,

mkimid

sr. member

Activity: 336

Merit: 250

Have A Nice Day

Quote from: ?? on ??

Quote from: CommanderVenus on February 11, 2015, 08:34:17 PM

Currently someone could jump on the network with a big hashrate and gobble up 20 blocks until the difficulty goes up and then leave the other miners to struggle with the higher difficulty. Wash rinse repeat. right?

It could be a wise decision. Any drawbacks though?

+1

It makes the block time is stretched by 120-130% (36-39 sec)
this problem is happening due to the overall network hash is just 60-80MHPS,

WorstCases

newbie

Activity: 1

Merit: 0

Guys, I have massive problems syncing the Wallet.

Yesterday I did download the current Version from the bitquark site.
I did make a subfolder "data" (I don't want to use up drive c)
I did make a .bat file and start the program with

Code:

bitquark-qt.exe -datadir=./data/

Wallet only shows "No Block SourceAvailable an 58 weeks behind. The 58 weeks make me wonder, because with a new installation it should be more. 58 weeks behind is what my local (old) installation is showing also. Maybe the wallet is somehow using some data from the previous installation which I didn't delete yet.
The previous installation is storing it's data in the standard directory on drive C and I don't see why the new program which is started with pointing to it's own data folder can utilize any information from the other installation.

I did create a bitquark.conf file and put it in the data folder. Do I have to do anything else to make the program read the conf-file?
I'm stuck!
The conf-Contint is:

Code:

rpcuser=BITQUARK
rpcpassword=PASSWORD
rpcport=9108
rpcallowip=127.0.0.1
rpcallowip=192.168.*.*
port=9596
server=1
listen=1
daemon=1
mintxfee=0.00001
mintxrelayfee=0.00000000
addnode=112.111.83.244:12256
addnode=103.24.88.5:50264
addnode=196.210.132.241:9596
addnode=220.166.171.10:9115
addnode=76.108.164.127:57864
addnode=81.154.205.63:55289
addnode=203.156.196.226:61682
addnode=69.8.51.75:35542
addnode=5.9.248.182:60084
addnode=124.234.48.148:14129
addnode=115.49.248.220:9596
addnode=64.53.248.79:9596
addnode=118.112.122.146:9596
addnode=196.210.132.241:9596
addnode=113.243.132.68:9596
addnode=125.70.106.2:9596
addnode=91.67.71.178:9596
addnode=42.239.119.231:9596
addnode=118.112.122.146:9596
addnode=98.119.203.187:9596
addnode=46.119.119.40:9596
addnode=114.66.195.170:9596
addnode=58.47.58.15:9596
addnode=62.210.123.27:9596
addnode=182.91.54.125:9596
addnode=122.192.218.120:9596
addnode=178.49.193.142:9596
addnode=174.107.145.6:9596
addnode=115.28.161.67:9596
addnode=210.195.183.143:9596
addnode=123.161.55.60:9596

I did disable the firewall already.

Where do the IP-Adresses in the conf-file come from? How does the sync work in general? Is one wallet trying to find other wallets to sync (torrent-style)? It would be great to gain some general understanding about the wallet. Some information or a good link would be great!

CommanderVenus

sr. member

Activity: 258

Merit: 250

Oh and i want to confirm that using pywallet to remove your unconfirmed transactions works with Bitquark. It deletes all transactions from your wallet then when you -rescan it makes it so that your wallet only reflects what actually got through to the blockchain and confirmed.

https://bitcointalksearch.org/topic/guide-delete-your-0unconfirmed-transactions-in-30-seconds-35214

CommanderVenus

sr. member

Activity: 258

Merit: 250

Quote from: BitQuark on February 12, 2015, 12:03:21 AM

ASIC coming soon for X-series algorithm coins!! This would also include Quark algorithm coin!

Disgusting.

BitQuark

hero member

Activity: 716

Merit: 501

ASIC coming soon for X-series algorithm coins!! This would also include Quark algorithm coin!

BitQuark

hero member

Activity: 716

Merit: 501

Quote from: CommanderVenus on February 11, 2015, 08:34:17 PM

Currently someone could jump on the network with a big hashrate and gobble up 20 blocks until the difficulty goes up and then leave the other miners to struggle with the higher difficulty. Wash rinse repeat. right?

It could be a wise decision. Any drawbacks though?

Yeah that's the exact concern that I have. 20 block retargeting allows drop in miners to clean house and then leave smaller miners to pick up the pieces. As far as I know, there aren't any drawbacks to DGW3. If I can get everything up and going in time, I will release BTQ-r19 and have the DGW3 start at block 1,000,001.

CommanderVenus

sr. member

Activity: 258

Merit: 250

Currently someone could jump on the network with a big hashrate and gobble up 20 blocks until the difficulty goes up and then leave the other miners to struggle with the higher difficulty. Wash rinse repeat. right?

It could be a wise decision. Any drawbacks though?

BitQuark

hero member

Activity: 716

Merit: 501

How do you guys/girls feel about changing the difficulty retargeting to DarkGravityWave3 (DGW3) Huh

So instead of the difficulty retartgeting every 20 blocks, it will retarget every block.

Thanks,
BTQ Dev

CommanderVenus

sr. member

Activity: 258

Merit: 250

Ive been consolidating many p2pool payouts using "sendfrom". Its the easiest method i have come up with.

BitQuark

hero member

Activity: 716

Merit: 501

Quote from: lordmick on January 11, 2015, 01:32:47 PM

i have a problem.. 2 transaction has not been send..... what can I do?

Do you have all your coins consolidated to one BTQ Address??
-OR-
Does it show what address is associated with the stuck coins under "send" >> coin control feature "inputs"...the address should show "0" confirms.

CommanderVenus

sr. member

Activity: 258

Merit: 250

Quote from: Youghoor on January 23, 2015, 11:00:56 AM

Quote from: lordmick on January 11, 2015, 01:32:47 PM

i have a problem.. 2 transaction has not been send..... what can I do?

Wait for a bit more and then it will get confirmed.

The bitquark blockchain confirms transactions within a couple minutes usually because blocks get solved or created so quickly. If your transactions havent been confirmed yet, they probably wont. It has something to do with the fee sent along with your transaction.

I have some transactions still unconfirmed from months ago. Your local client will think that all the inputs used in those transactions unavailable. If you run "listaddressgroupings" in the console it will give you all the addresses in your wallet and their amounts and if you have unconfirmed transactions, you will be able to see that the numbers are conflicting if you compare amounts to the blockchain.

Just now i ran bitquark with the -rescan option. Ive done some reading and that is supposed to be one way to remove unconfirmed transactions, but it didnt work for me.

If you are a windows user, just go into the properties of your bitquark shortcut and edit the target to look like this -
"C:\Program Files\BitQuark\bitquark-qt.exe" -rescan

Another method i found is to use pywallet described in this thread https://bitcointalksearch.org/topic/guide-delete-your-0unconfirmed-transactions-in-30-seconds-35214
I havent tried it and theres no guarantee that it will work with the bitquark wallet anyway.

BitQuark

hero member

Activity: 716

Merit: 501

Quote from: ZeroFossilFuel on January 27, 2015, 11:45:37 AM

So the net hash rate is ~750 MH/s and the weminebtq pool rate is roughly 10% of that. Looks like there's some interest out there.

Have you seen the volume on C-Cex?? 3.75 BTC buy volume over the past 12 hrs!

ZeroFossilFuel

sr. member

Activity: 346

Merit: 250

So the net hash rate is ~750 MH/s and the weminebtq pool rate is roughly 10% of that. Looks like there's some interest out there.

Topic: [ANN] [BTQ] BitQuark | Super secure hashing | CPU mining - page 20. (Read 162315 times)