Topic: [BIP] BipCoin. NOW LIVE. Mineable. CryptoNote. BipCot NoGov Licensed. - page 6. (Read 25052 times)

I think I just got some, solo-mining, ~8.766

cool, I guess it's working...

I can't seem to get over 100# with a Phenom II X6 all 6 cores engaged... but I guess this is a 7yr old machine now... lol... max about 90#

what affects #rate the most?

Exactly. When more people are transacting you can use a higer rate. Early on one day I was testing with six people transacting at once and I was able to use a mixin of 5 once.

PM me a BipCoin address, I'll send you some squittens, and you can let me know when you get it. Same to anyone else reading for, let say, the next 4 hours.

For what it's worth, I sent a few bips from one wallet of mine to another to test and received them ok.  I sent them using the CLI wallet with a mixin value of 2 (anything higher than 2 doesn't seem to work yet, probably because of the low volume of transactions).

AFAIK I must get them back soon after 24h or 48, damn it i can't remember. CN code is a mess actually, if you wanted your own monero, why not use its code instead.

Were those coins mined on the pool that had an IP address for a URL? Those are the coins from that pool that forked. Wasn't my pool. Someone set up a pool and said "Hey, I set up a pool." I did say "cool!" and post it around. So I take some responsibility in it.

Also, we're working on improving the coin over the next week to reject unspendable transactions instead of trying them over and over.

Solo-mined coins, and coins mined on the pool that had a dot-org URL should be spendable.

I tried to send some coins yesterday and they are still unconfirmed.

I certainly do admit BipCoin's code is not perfect. It's freaking version .0001, lol.
We're working on an update that will hopefully make it less sensitive to outside issues.

Thank you for being patient, y'all.
MWD

--Yeah it happened whenever you got over 51%, but how come your pool ended up 65 blocks ahead of the chain?

--How come a pool after that (run by a guy who runs a pool for CryptoNote coins and really understand them) didn't end up ahead of the chain? And his explorer (driven by his pool) kept locked in with the block we were seeing in our wallets?

--How come you basically apologized to me saying you didn't understand CryptoNote coins and didn't want to run pools for them again?

Come on man, I was EXTRAORDINARILY cool to you about this. I didn't blame you or bash you personally at all.

You basically told me you didn't understand CryptoNote coins. I even still like you and have said nice thing to you after it, and about you to others after it. You meant well, it just didn't work.

I'm not going to start copying and pasting your private messages to me onto the forum in public to prove what you said, but take ownership for what happened. Or at least don't now try to push it off of you having any part in it.

And even if it wasn't on your end at all as you claim, how come you didn't shut down the pool after the first night when I asked to? You ran it a second night and forked and ended up with people mining un-spendable coin a second time. Even if it was entirely a problem on the coin's end, why would you do that if you knew there was a problem?

It's those un-spendable coins that are causing the constant errors now.

We're working on an update that will stop those error coins from affecting the network, and harden the network against any kind of pool being a problem.

I'm taking SOME ownership in this. I'm amazed you won't take ANY in public after you did with me in private.

MWD

in bitcoin 51% attacks that caused forks there were a couple they always went with the longer chain or for people who dont understand the pool that had the most hash at the time of the fork

Even so, why is it that most clients stick to the "normal" shorter chain while the pool's fork keeps getting longer and longer??
Shouldn't they switch to the longer one, making it the new normal?
Whether or not it would be desirable, I still don't understand why it ended up being such a clusterf*ck. Can someone explain?

My pool was not "misconfigured" your difficulty is to low to sustain a pool when the network diff gets low at night the pool gets almost 90% of the hash power or more and causes forks please dont bash me for something you clearly dont understand

Your windows gui wallet won't load for me on win64. the error it pops up with is: “failed to start because it could not find or load the Qt platform plugin “windows”.

Any other windows gui x64 wallet i've tried has worked before. Solutions?

Some guy ran a mis-configured pool for a few days about 5 days ago. People earned coins that were on his fork, no longer part of the real chain. I think people are trying over and over to spend them.

Will ignore them so they don't keep trying. Notice some of them are the same ones over and over. Mainly this work will be done on the seed nodes.

in cryptonote algo coins,the transaction take ~72 hours trying to be confirmed and then return to main balance of the owner.
Up to him to try again to spend them (will be very shitty from his part)

It's like those email messages "could not be delivered. will try for three days."

Still fallout from that fork. Someone's trying to spend it, and it tries over and over. Next version should minimize those.

As you use more threads, the per thread performance drops even though total still increases.

Using all 4 threads even doing nothing else would not get me to 180h but maybe 140h

Also I am not sure how the processor allocates the core threads when it has hyperthreading.
My i5 doesn't have HT so 1 thread = 1 core. But if you have an i7 and you use 4 threads it might use 2 cores most of the time and average hash calculation per thread will suffer.
I still believe it will do better in total performance though.

My i7 5930 (when I use it) performs just like yours

I'm not doing quite that well, but I did find one within about 8 minutes of starting to mine tonight.

ah!