Yes I've set up the server, added all required server features/roles/addons. Installed SQL Express, SSMS, etc. imported the SQL files (MS Word document out of date, refers to a .bak file that is NOT in source) Figured out it was the Schema that needed to go first then the data (basic DevOps) Imported the data and schema without issue Built the source from the solution except there are missing front-end files contained either in the solution build, or the source files Set up IIS7, dropped in test file and am able to view it but there is no default.aspx, no login.aspx --- where are the front end files?? Have they been removed due to security reasons so people cannot reverse engineer the front end? I feel like a successful project will keep its front end github source up to date. All files are there. The only thing missing in github is one query - I will add it later today - the aspx files are there in the source, minersofmen did it without any help from me so you can see they were able to operate for quite a while. Please resync your source code to a desktop and traverse the folders. I will give you the query before end of day to get it running. EDIT: Here you go - these are the 2 things missing to get the pool running that is in Github: I n s e r t into Organization v a l u e s ('CDE6C938-9030-4BB1-8DFE-37FC20ABE1A0','BIBLEPAY POOL','Black',getdate())
Altr table work altr colmn solution v a r c h ar(max)
Rob |
|
|
|
Just update new version to Github...it not a impossible and reasonable.
The current version is most likely simply not ready for that. As Rob posted some days ago, some miners tried to cheat the pool, and after I looked into the current pool software, I understood how that worked. Problem of many open source software: you can easily find mistakes in them. Indeed, security by obscurity never works on the long run, but it might work for a short time. Give him some time, there are more important tasks on his list. The current version is OK for a private pool though. Thats what Slovakia is trying to do - by his greedy nature, have someone set up a private pool for him. If we were to start another public pool I would ramp up and get the service checked in for them, but the cancer idea is far more important right now. |
|
|
|
svirusxxx2 we are jumped to solo too ... few machines mining on pool,but when will be end in DC and then we can to fart to his pool ...
we need more transparency for all = we no need monopol 1 person guy´s pool ....
its pity that exists this coin with 1 pool only
are you kidding me,that on GitHub is old version? edit:// 2.0.3.0 is on GITHUB.... yes you have true about old version,damn it Robert: why are you hodling of newest version pool outside GitHub 2.0.3.6? all ppl thinks thats not transparency ... can you to add v 2.0.3.6 to GitHub please? thanks Rob is a busy man. I'm sure it will be updated. Also @Slovakia. I always gave you the benefit of the doubt, but you've crossed a line by trying to post Robs real name in an attempt to slander him. Just remember: I know your real name, 'mr bicycle'. Don't play games. The version on Github still works, its just a couple version back, right before we added the extended block hash. Sorry, but I recently added a windows service to check solutions, and pool sql batching for better performance, so that code is not ready to be checked in - and frankly - its going to change the install instructions - require addl support etc - so you can deal with the 'stable release' version that is already out there, its fine for private pools anwyay. This cancer integration is far more important than pool software and is my top priority. Who knows, it might do away with pools anyway. Why do things twice, and waste resources. |
|
|
|
Here is an interesting article about David Baker, director Protein Design, Univ of Washington: https://www.nytimes.com/2017/12/26/science/protein-design-david-baker.htmlSince Biblepay already helps orphans, and as I feel - just as Jesus Heals, Biblepay should investigate the healing aspect. Posing the question: What can Biblepay do to heal people? We can try to cure cancer, using our mining clock cycles.I'm currently working on the ability to partner with a well known organization that has over 1 million devices computing the cure. One of these organizations creates cross platform software, running on both linux and windows with a certain secure interface into the distributed computing cancer grid with credit monitoring abilities per server. I've been in contact with David Anderson, Berkeley for the initial design of the whitepaper. Now I am contacting David Baker, in hopes that we will come to an agreement for utilization of the "Cancer Computer" software his team has built. It is already running on over 50,000 servers, so it is well tested already, and the team has many achievements in the area of curing cancer, which I will outline. Since curing cancer is of paramount importance, I place this project at the highest priority level for Biblepay and will devote 100% of my time and effort into this over the next 2 weeks as we focus on integrating with Univ of Washington and the Cancer Computer initiative into Biblepay core for testnet testing. This will result in a hybrid of Proof-of-Loyalty/Proof-of-Distributed-Computing for our core algorithm. Of course, we will vote on all of the important aspects such as : modifying consensus, consensus payment mechanisms, and pool ramifications. But first, I need to finish the proof of concept. If the proof of concept is successful, I will modify our roadmap to have a Cancer Fighting release set for June 2018, and move Stratis proof-of-concept back to September 2018. All credit goes to Jesus, the most high. This is pretty awesome. It's the kind of thing I wish others would have thought of (well, there are a few Distributed Computing coins I remember seeing). The only thing that is a shame is the loss of the PoBH algo, but the gains for all are totally worth it! We can still use Proof-of-bible-hash for security, since we still need blocks to be solved on a regular basis etc. Ill add this to the whitepaper. |
|
|
|
SouthXchange is exchange without Volume.
At the very least we just need an exchange where everyone can buy and sell, C-CEX is live with us but still has new user registration disabled, CoinsMarkets is still down Togo thats very relative. You will be not able to sell because there will be no buyers and you will not buy because there will be not sellers without bigger daily volumes. List to this exchange is useless from traders point of view. There are a lot of people who to buy but currently cant, and there are a lot of miners who want to sell to pay their monthly server costs. Ive seen both sets of people in the forums, reddit and discord. Im not sure what you are trying to say. What would you advise as the course of action? I agree with Togo, I am receiving 5 emails per day (some days) from investors who cant buy BBP because they cannot become a new user at ccex. If there is truly a demand for BBP, they these users may fuel the impetus to make BBP a higher volume crypto on Southexchange because they will make their own market, as long as southxchange is a reliable exchange. |
|
|
|
Tom, I asked SouthXChange for the New Coin Application form so we can get listed quick, and Support sent me an email (alluding to the fact they would list us for the .15 fee) :
Please sign up in our exchange and fund your account.
So I assume if you want to go in and cash those BTC in, and go ahead and fund your trading account, then I can reply and say that you are the ambassador for Biblepay, use this account number, and make us live.
Okay sounds good, but is the southXchange listing "entry" fee 0.1 or is it 0.15? Here's what I got from them ... "Thanks for contacting us. We can add this coin. The entry fee is 0.1 BTC. Your SouthXChange Support Team" Just to make sure I do this correctly ... I should transfer the 285K BBP to my C-CEX account and convert it to BTC, then transfer the BTC to my southXwest account? Thanks Tom. Yes if they said .10, then just go with .10. Yeah, I would sell the BBP on the exchange and put .11 in your trading account, then follow up from the same mail and say OK Im funded, lets get BBP live! Thanks dude. |
|
|
|
Here is an interesting article about David Baker, director Protein Design, Univ of Washington: https://www.nytimes.com/2017/12/26/science/protein-design-david-baker.htmlSince Biblepay already helps orphans, and as I feel - just as Jesus Heals, Biblepay should investigate the healing aspect. Posing the question: What can Biblepay do to heal people? We can try to cure cancer, using our mining clock cycles.I'm currently working on the ability to partner with a well known organization that has over 1 million devices computing the cure. One of these organizations creates cross platform software, running on both linux and windows with a certain secure interface into the distributed computing cancer grid with credit monitoring abilities per server. I've been in contact with David Anderson, Berkeley for the initial design of the whitepaper. Now I am contacting David Baker, in hopes that we will come to an agreement for utilization of the "Cancer Computer" software his team has built. It is already running on over 50,000 servers, so it is well tested already, and the team has many achievements in the area of curing cancer, which I will outline. Since curing cancer is of paramount importance, I place this project at the highest priority level for Biblepay and will devote 100% of my time and effort into this over the next 2 weeks as we focus on integrating with Univ of Washington and the Cancer Computer initiative into Biblepay core for testnet testing. This will result in a hybrid of Proof-of-Loyalty/Proof-of-Distributed-Computing for our core algorithm. Of course, we will vote on all of the important aspects such as : modifying consensus, consensus payment mechanisms, and pool ramifications. But first, I need to finish the proof of concept. If the proof of concept is successful, I will modify our roadmap to have a Cancer Fighting release set for June 2018, and move Stratis proof-of-concept back to September 2018. All credit goes to Jesus, the most high. |
|
|
|
|
Tom, I asked SouthXChange for the New Coin Application form so we can get listed quick, and Support sent me an email (alluding to the fact they would list us for the .15 fee) :
Please sign up in our exchange and fund your account.
So I assume if you want to go in and cash those BTC in, and go ahead and fund your trading account, then I can reply and say that you are the ambassador for Biblepay, use this account number, and make us live.
|
|
|
|
|
I see Pool | Reports | Difficulty History is rising quite sharply. Good job guys.
|
|
|
|
Thanks Dave_bbp, that helps a lot.
Weird thing happened last night, I had another solo mining lump sum in my transaction list with the dove icon, the coins were "immature", but this time rather than mature and move to my balance they simply disappeared after a while.
Any ideas why? Is there some action that I can take from the "repair wallet" to retrieve?
It sounds like you were running the latest version (1086+). If that was the case, this is very very rare, its called an orphaned block. (Pardon the pun). This means you actually found a block solo mining but it was stale, and at the same very instant someone else found that block so the wallet erased yours (because they beat you to the punch system wide). Basically, whatever block is confirmed by the supermajority (51%+) first, becomes the next block in the chain. You would have to look at your log for the block you found then a reorganize, then a new pindexbest entry to verify this is indeed what happened. |
|
|
|
|
Tom, I cant find the SouthXChange new coin Add page anywhere. Have they gotten back to us?
Anyone know where we can find it? Ill fill it out if we want to "jump on the camel" with .15 btc and be listed 24 hours later.
|
|
|
|
|
Wow, difficulty is rocketing higher now. Take a look at the Diff history. I see spikes hitting 6000 now.
|
|
|
|
|
Please monitor the pool now. For more performance I enabled SQL batching.
|
|
|
|
SVK Noko may be trying link machines so they'll work together cooperatively like a pool does - to solve the block.
I guess, but really the math of it is that 4 machines working independently have an equal chance to solve a block at 4 machines working in unison. Having a common wallet alleviates the need to check more than one machine to see if any of them succeeded. That's why I'm curious if he has some other reason. Question ... does a pool assign different segments of the mathematical puzzle to each miner, so that no two miners will propose the same possible answer to the puzzle? Yes, as long as the miner has more than .10 bbp in the wallet. What makes the block template unique is: Block timestamp, Block transactions, CoinbaseTxToSelf Up til 1.0.8.4, we relied on the Timestamp and the transactions. However as we grew, and we have transactions that hardly change (IE not much in memory pool), we added the last feature (coinbase tx to self). The other side of the equation is Pool only accepts distinct nonce solutions so that two miners cant solve the same fractional share. Otoh, let me give you an example where a problem exists (situation b: ) 100 miners running 1.0.8.7 with 0 in the wallet, all synchronized to NTP (network time). They will have a propensity to create the same block template (because unix time would match on a lot) and with our Low transaction count (IE not many people buying coffee with BBP right this second), those miners would all be mining the same block- so some would get rejected in the pool - and would not be helping us solve the block. So situation A above is much nicer.... Okay thank you, that explains a lot. Question ... for a pool account with more than 1 miner, it would be better to either a) have more than .10 bbp in each miner wallet, or b) all miners share a wallet with at least (how much?) bbp in it? Well since we are still without POL the amount does not matter, the coinstake generator is just saying give me some coins with age > 24 hours that equal more than .10% of the wallet balance. That particular utxo chosen creates a TXID that changes the merkleroot for that particular wallet. So then that baseblockhash is unique systemwide. The miner will then just change the timestamp and the nonce of that block. You can see the baseblockhash in getmininginfo now. However, in this system it would be slightly more helpful to have distinct wallet.dat files on each miner - but - this is sort of overkill - as I feel that if you have more than .10 bbp, you are already pretty much unique system wide. It would come into play if you had 100 machines or more, I would put a different wallet.dat on each 25 or so machines, so to ensure that each miner segment has a distinct UTXO to pull in the coinstake. |
|
|
|
If you guys checking the leaderboard now will see the shares showing strange ... 1 too high and all the rest too low. That mean the top has HPS too much and all the rest no chance to mining ?
Yep, pool seems to be down or at least have a major hickup right now. All my miners are "gone" from my leaderboard, but some of my hash power miraculously shows up in the overalls. But then again the same thing happened yesterday and after that the pool had a nice run in finding lots of blocks, so we'll see...  Well it cant be down because its processing 125 queries per second right now, and it received a block solved 2 mins ago. The question is it being ddossed or not. There is nothing strange in the log. |
|
|
|
im was w/notification and 1 refresh helped with watchdog expired  Rob: your tutorial for pool is horrible: nor can we be surprised who compiled pool and tutorial for pool=1 big chaoz= bordel ...every who tried it was totally messed up, i hope that you dont work like pilot, operator in nuclear power plant or doctor etc ...  can you explain where is problem with superadmin account or others users-account which exists in DB but doesnt working connecting to pool? source telling that mail to you i hope that your opensource is for free and no FEES/ MONEY Judging from two comments here that you were not able to create your own Sanctuary, I would not expect you to understand the instructions to create a pool. (You bashed the sanctuary guides Togo and I created as well). |
|
|
|
SVK Noko may be trying link machines so they'll work together cooperatively like a pool does - to solve the block.
I guess, but really the math of it is that 4 machines working independently have an equal chance to solve a block at 4 machines working in unison. Having a common wallet alleviates the need to check more than one machine to see if any of them succeeded. That's why I'm curious if he has some other reason. Question ... does a pool assign different segments of the mathematical puzzle to each miner, so that no two miners will propose the same possible answer to the puzzle? Yes, as long as the miner has more than .10 bbp in the wallet. What makes the block template unique is: Block timestamp, Block transactions, CoinbaseTxToSelf Up til 1.0.8.4, we relied on the Timestamp and the transactions. However as we grew, and we have transactions that hardly change (IE not much in memory pool), we added the last feature (coinbase tx to self). The other side of the equation is Pool only accepts distinct nonce solutions so that two miners cant solve the same fractional share. Otoh, let me give you an example where a problem exists (situation b: ) 100 miners running 1.0.8.7 with 0 in the wallet, all synchronized to NTP (network time). They will have a propensity to create the same block template (because unix time would match on a lot) and with our Low transaction count (IE not many people buying coffee with BBP right this second), those miners would all be mining the same block- so some would get rejected in the pool - and would not be helping us solve the block. So situation A above is much nicer.... |
|
|
|
pool is dead again, same like 2 days ago...
it is not coincidence...
I wonder if it's coincidence that a large proportion of the MN's have just just gone to WatchDog Expired states ?? ENABLED 36
NEW_START_REQUIRED 3
WATCHDOG_EXPIRED 83
PRE_ENABLED 0
UPDATE_REQUIRED 0
EXPIRED 0
Those might be running 1.0.8.2. If the node actually Stopped, their payments will stop. Anyone who owns one of those 20 nodes, please come online and tell us what happened. Either way you have to upgrade to 1.0.8.6 to stay up without a crash. The problem was fixed in 1.0.8.6 |
|
|
|
|
I think we should stay away from Binance. They seem to be run by Greedy non Christians.
I got in touch with "Carlos - JP Support 1022" and explained how I was scammed by someone posing as Sr. Manager for Binance, created a ticket, sent the backing info and even created a new-coin application, and all I received back today was "Sorry, nothing we can do for you. "
They could care less.
|
|
|
|
we still dont know what happens around block 27815 when pool gets alive rob did you investigated this? root cause must be there I didnt see anything funny, except more traffic, and now less traffic. It has anti-ddos, but its possibly getting ddossed very hard. I have to check the logs again, let me take a look. |
|
|
|
|
Show Posts
