[ANN] [BEN] Benjamins ◄ SHA-256 ►◄ BOUNTY AVAILABLE to make BEN merge mineable!!

[itsunderstood]

[1714697360]

1714697360

[1714697360]

1714697360

[1714697360]

1714697360

[1714697360]

1714697360

[1714697360]

1714697360

[Paysha]

https://i.imgur.com/T8x9aXv.jpg

Ideally, yes 

[itsunderstood]

Ideally, yes 

So then,

VeeSA says: "Hur durr, maybes needs encryptions?  Much dollars needed!"

And, yet, that is what the SHA hashcube DOES: Encryption.

The blockchain of some good and true coin (not debauched by diff forks) if it can deliver true security where Visa hath fumbled (all their 1000s customers robbed the last holiday) will see an adoption like none every before.  AND YET, that coin must think ahead as to how to provide TX identifiers that are true, but which do not contain payload that contains user data.

From a legal perspective, if you look at the crushing penalties for fumbling customer data, well, it makes one want to become a lawyer (haha not really) because of the sheer volume of litigation which is pending against companies that now owe the states millions of theorized-legal-dollars in future terms, because of recent data fumblings.

All acceptors of any customer identifiable data, shall suffer hard fines if they screw that fiduciary duty up.  That is what the code says.  So, the coin which brings POS security, will exploit the current milieu which is one of customer pain and theft-sufferings.

[Paysha]

Ideally, yes  

So then,

VeeSA says: "Hur durr, maybes needs encryptions?  Much dollars needed!"

And, yet, that is what the SHA hashcube DOES: Encryption.

The blockchain of some good and true coin (not debauched by diff forks) if it can deliver true security where Visa hath fumbled (all their 1000s customers robbed the last holiday) will see an adoption like none every before.  AND YET, that coin must think ahead as to how to provide TX identifiers that are true, but which do not contain payload that contains user data.

From a legal perspective, if you look at the crushing penalties for fumbling customer data, well, it makes one want to become a lawyer (haha not really) because of the sheer volume of litigation which is pending against companies that now owe the states millions of theorized-legal-dollars in future terms, because of recent data fumblings.

All acceptors of any customer identifiable data, shall suffer hard fines if they screw that fiduciary duty up.  That is what the code says.  So, the coin which brings POS security, will exploit the current milieu which is one of customer pain and theft-sufferings.

You would have been good to have in our meeting a few weeks ago when we were discussing a lot of this. That's when we decided to trademark Paysha and register the DBA individually with FinCen

Transaction details only show the address it's coming from and going to. That's like writing a check, as that also has your account information on it. It goes back to what I was saying earlier, though, about the lockbox working one way. Even with your routing and account information, they can only put money in, not take it out.

All information, transactions and payments are verified with multiple layers in our system through several random identifiers, which I won't get into in public for obvious reasons

POS speed like it is with cards won't be possible operating this way, at least not with the current list of coins. There are a few options to do it, but that involves holding funds, which is not something we are looking to do right now. After the recent MtGox bullshit, we want to get the money to the seller as quickly as possible with no delays and not even give an opportunity for us to "misplace" it due to full automation

Another advantage to longer block times is more secure block chains, which is what Paysha is focused on, rather than transaction speed. As said earlier, most merchants are used to 2-3 days for ACH to transfer, so even at a few hours, we are still improving the wait time, not to mention lowering their merchant and transaction fees by +/- 50% depending on volume of credit and debit sales

On a legal note, we are only keeping the minimum amount of required information to keep both our website and payment structure in compliance, and again, that is only for our cold stored records, not to sell or share with anyone else, nor be stored online and accessible to attacks

[itsunderstood]

[...]

You would have been good to have in our meeting

[...]

On a legal note, we are only keeping the minimum amount of required information to keep both our website and payment structure in compliance, and again, that is only for our cold stored records, not to sell or share with anyone else, nor be stored online and accessible to attacks

That's so awesome, because, typically people hate me on their conference calls.  It's like inviting a spark to a dry forest.

But, your policies above seem good.  Fumbling customer data is a major foul.

I am ready for any chat or meeting at any time.

[iGotSpots]

Target also didn't encrypt any information

[AllAboutTheBenjaminsBaby]

Any ETA?

[CryptoGuy]

Does anyone know what happened with ben.pitythepool.com? They're still accepting my shares but the website is down.

[kovert]

Does anyone know what happened with ben.pitythepool.com? They're still accepting my shares but the website is down.

Same for me its been shady for a few day.

Might give up all this crypto bollox

[Mortimer452]

Does anyone know what happened with ben.pitythepool.com? They're still accepting my shares but the website is down.

PityThePool has been under intense DDOS attacks for the past week - every day for about 6-12 hours.  We've been holding up under most but today was a monster and the web interface was definitely not responding most of the day.  Stratum mining has been operational during the attacks, as are cronjobs for payouts and such, so as long as your miner says you're connected you're still mining & getting paid.

Back online for now, hopefully for good

[AllAboutTheBenjaminsBaby]

Does anyone know what happened with ben.pitythepool.com? They're still accepting my shares but the website is down.

Mining seemed to be ok. Block explorer is getting attacked a lot recently, too

[iGotSpots]

I've had a small miner on pity for a while. Even when front end goes down mining seems fine

[CryptoGuy]

I've been busy and haven't checked in a couple days so I wasn't sure. I won't worry about it for now but I should probably lower my payout threshold so it doesn't take so long between payouts.

Edit: The site is up now but the minimum payout is only able to be set to 100. 

[AllAboutTheBenjaminsBaby]

I've been busy and haven't checked in a couple days so I wasn't sure. I won't worry about it for now but I should probably lower my payout threshold so it doesn't take so long between payouts.

Edit: The site is up now but the minimum payout is only able to be set to 100. 

Send him a message. All the pool ops listed in the OP are extremely helpful

[Mortimer452]

I've been busy and haven't checked in a couple days so I wasn't sure. I won't worry about it for now but I should probably lower my payout threshold so it doesn't take so long between payouts.

Edit: The site is up now but the minimum payout is only able to be set to 100.  

Send him a message. All the pool ops listed in the OP are extremely helpful

I have lowered the min payout to 1 BEN - sorry it's an MPOS default I just forgot to change

These DDOS attacks are getting really annoying.  They were really only attacking one pool but since the web front-end for all my pools is the same server they pretty much all went down.

I'm going to scale out a bit with the pools so one getting attacked doesn't take everything down.  I own two entire Class C address blocks no reason why I can't setup each pool with its own IP

[AllAboutTheBenjaminsBaby]

I've been busy and haven't checked in a couple days so I wasn't sure. I won't worry about it for now but I should probably lower my payout threshold so it doesn't take so long between payouts.

Edit: The site is up now but the minimum payout is only able to be set to 100.  

Send him a message. All the pool ops listed in the OP are extremely helpful

I have lowered the min payout to 1 BEN - sorry it's an MPOS default I just forgot to change

These DDOS attacks are getting really annoying.  They were really only attacking one pool but since the web front-end for all my pools is the same server they pretty much all went down.

I'm going to scale out a bit with the pools so one getting attacked doesn't take everything down.  I own two entire Class C address blocks no reason why I can't setup each pool with its own IP

Told you he would respond soon! Thanks for paying attention to the miners

[vual]

....The problem with visa and mastercard is any 12yr old russian script kiddy can fire up sqlmap or similar tool and with no actualy skills in sql let alone hacking go out and scan all of africa and third world countrys for shitty configured webstores, then with the press of a button dump the data, loginto tor and sell it to carders....
I wouldnt blame visa as much as i would blame shitty third world web devs, pay penuts get monkeys.

Paysha will not be vunrabile to such exploits, even if the data was dumped the passwords (one would hope would be hashed) so "theif" has nothing....

Also in regards to mastercard and visa alot of the data for sale is from actaull employees and stoer owners they install skimmers on there own POS and harvest the data then sell. You will find 90% of card data comes from dodgy store owners and employee's the rest from third world countrys..... many a times swim has found a thirdworld webstore running mysql as root user and hosting 100+ pages from the same DB.... you would be suprised how many well known USA sites are hosted in a dodgy thirdworld shared hosting enviroment.


For instance...
If you use the SAME PASSWORD YOU USE HERE anywhere else then you are fucked, ie: if you use the same password from bitcointalk on paysha, say goodby to your funds, this isnt paysha's fault, its yours. Hacker hacks this site bitcointalk, dumps DB uses his "bitcoin mining" ASICS to crack your passowrd hash with salt then uses bot to try combo's on a list of 100+ bitcoin related sites, stores results and laughs all the way to the bank, but who is to blame? not paysha but you for using the same dodgy password for everythign you do online...... No asic could crack my 16 + char password, and its different for everysite.

[vual]

Wow! You seem to know a lot about computer things, the world, and all....

My question is, why are you still mining and supporting BEN when the next diff retarget is not to occur before 360 days from now?  (1997 blocks x 4h 20min).   I am really confused. 

"In this world nothing can be said to be certain, except death and taxes." - Benjamin Franklin

[Paysha]

....The problem with visa and mastercard is any 12yr old russian script kiddy can fire up sqlmap or similar tool and with no actualy skills in sql let alone hacking go out and scan all of africa and third world countrys for shitty configured webstores, then with the press of a button dump the data, loginto tor and sell it to carders....
I wouldnt blame visa as much as i would blame shitty third world web devs, pay penuts get monkeys.

Paysha will not be vunrabile to such exploits, even if the data was dumped the passwords (one would hope would be hashed) so "theif" has nothing....

Also in regards to mastercard and visa alot of the data for sale is from actaull employees and stoer owners they install skimmers on there own POS and harvest the data then sell. You will find 90% of card data comes from dodgy store owners and employee's the rest from third world countrys..... many a times swim has found a thirdworld webstore running mysql as root user and hosting 100+ pages from the same DB.... you would be suprised how many well known USA sites are hosted in a dodgy thirdworld shared hosting enviroment.


For instance...
If you use the SAME PASSWORD YOU USE HERE anywhere else then you are fucked, ie: if you use the same password from bitcointalk on paysha, say goodby to your funds, this isnt paysha's fault, its yours. Hacker hacks this site bitcointalk, dumps DB uses his "bitcoin mining" ASICS to crack your passowrd hash with salt then uses bot to try combo's on a list of 100+ bitcoin related sites, stores results and laughs all the way to the bank, but who is to blame? not paysha but you for using the same dodgy password for everythign you do online...... No asic could crack my 16 + char password, and its different for everysite.

Wow! You seem to know a lot about computer things, the world, and all....

My question is, why are you still mining and supporting BEN when the next diff retarget is not to occur before 360 days from now?  (1997 blocks x 4h 20min).   24h for a transaction to confirm.  20 days for a mined coin to mature.... and the dev-team that doesn't want to do anything about the diff issue with BEN? 

I am really confused.  

That is only due to low hash rate. Although you are quite off

Est. Avg. Time per Round (Network)   1 hour 16 minutes 3 seconds

[Paysha]

That is only due to low hash rate. Although you are quite off

Est. Avg. Time per Round (Network)   1 hour 16 minutes 3 seconds

Are we looking at the same coin?  

http://ben.pitythepool.com/index.php?page=statistics&action=pool

indicates that it takes well over 4h per block - and they are finding ALL the blocks...

Yea, once an hour on average

24211   nickbiker   07/03 01:58:15   23,719
24210   nickbiker   07/03 00:56:08   109,892
24209   nickbiker   06/03 20:09:18   66,989
24208   HenryFord   06/03 17:15:07   22,989
24207   HenryFord   06/03 16:12:34   125,696