*Please note that this update may not include every work by every developer as it may have been simply missed or are currently worked on private repositories.

 

GitHub Activity

GUI (next gen)

  • PR #954 [GUI] [Model] New Wallet UI – has been submitted by core developer furszy and is currently being reviewed / worked on. This will be a brand new UI/UX wallet, designed in collaboration with Krubit UI and UX designers and written from scratch in Qt by core dev furszy and Krubit front-end developers. It is targeted to replace the current GUI starting from v4.0.0 release. More info and a full demo video can be seen HERE

Staking

  • PR #952 – [Minting] Prevent potential negative out values during stake splitting – has been submitted by community developer CaveSpectre11 and is being reviewed / worked on.
  • PR #955 – [Core][Script][Wallet][RPC][Tests] Cold Staking – has been submitted by core developer random.zebra and is currently being reviewed / worked on. This customized staking feature (name subject to change) allows a mutually agreed online wallet to stake coins from an address that it has been given delegation to stake from. This provides extra security for stakers while still requiring a full node online wallet. More info on Cold Staking can be found on its Wiki and there is an ongoing forum discussion as well.
  • PR #958 – [Staking] Modify miner and staking thread for efficiency – has been submitted by community developer CaveSpectre11 and is being reviewed.

Core Wallet

  • PR #956 – [Core][Qt] Add HD Wallet support – has been submitted by community developer akshaynexus and is currently being reviewed / worked on. This is a highly requested feature where it provides users an option to backup and restore the entire wallet (all associated addresses and their balances) using a multi-word seed phrase instead of more complex file-based or private-key methods.

Zerocoin Protocol

  • PR #936 “[zPIV] PublicCoinSpend v4 – Coin Randomness Schnorr Signature” has been submitted by core developer random.zebra and is currently being reviewed / worked on. This advanced function will allow spending of legacy zPIV v1 (minted prior to 3.1 release) back to PIV. Functional tests on regtest for this change is being prepared.

Qt / RPC

  • PR #950 [Qt] [RPC] Fixup budget proposal URLs that are lacking scheme – has been submitted by community developer CaveSpectre11 and is being reviewed.
  • PR #953 – [RPC] [Wallet] AutoCombineRewards fixes and Improvements – has been submitted by community developer CaveSpectre11 and is being reviewed / worked on. This enhances the AutoCombineRewards function allowing the user to configure how often to run the scan, and the amount to combine each time it executes; as well as adding a One Shot option to just run it once at startup.
  • PR #957 – [Build] Add info about ‘–with-unsupported-ssl’ – has been submitted by core developer Warrows and has been merged to master.
  • PR #963 – [WIP][RPC] Add PoS support to transaction utilities – has been submitted by community developer CaveSpectre11 and is being reviewed.
  • PR #964 – [Refactor] Combine parameter checking of budget commands – has been submitted by community developer CaveSpectre11 and tracked by Issue #966.
  • PR #965 – [RPC] Correct issues with budget commands – has been submitted by community developer CaveSpectre11 and tracked by Issue #966.

Secure PIVX Masternode Tool (SPMT)

  • New Release! SPMT version v0.5.0 with new Trezor support is has been released! This tool allows you to setup PIVX masternodes with the collateral safely stored in a hardware wallet such as Ledger Nano S and Trezor Model One and Model T.

iOS Wallet

  • PR #19 [Build] Add basic TravisCI support – has been committed to master.

Scripts & Tools

  • PR #20 [Tools] Add github-merge.py script – has been committed to master.
  • PR #947 [Scripts] Sync github-merge.py with upstream – is being reviewed.

Tests

 

Nota del Editor

Hemos tenido un significativos avances de los desarrolladores en las últimas dos semanas, con numerosas nuevas características y correcciones, incluidas numerosas contribuciones de los desarrolladores de nuestra comunidad CaveSpectre11 y akshaynexus. Es realmente increíble ver una nueva sinergia entre los desarrolladores core y los desarrolladores de la comunidad y espero que más desarrolladores se unan a nuestro proyecto. Recuerda que, PIVX es de código abierto y agradece todas las contribuciones de la comunidad, ¡sin mencionar que una parte del presupuesto en la propuesta del equipo de desarrolladores core está reservada para el agradecer el trabajo de la comunidad de desarrolladores!

La postura de PIVX sobre la privacidad, no ha cambiado. Esto significa es que la importancia de la privacidad de las transacciones, sigue siendo una prioridad para PIVX. Sin embargo, primero debemos asegurarnos de no dejar a nadie atrás.

Lo que queremos decir con esto es que debemos asegurarnos de que todos los zPIV restantes en poder de los usuarios, puedan gastarse de forma segura en PIV. Con nuestra última actualización 3.3.0, se habilitó el gasto de zPIV v2 y esto dio como resultado que el saldo de nuestra red zPIV cayera de 4,7 millones de zPIV a 1,58 millones de zPIV en menos de 3 semanas.

[Nota al margen] Tratando de adivinar a dónde fueron los 3.1 millones de zPIV convertidos; y considerando la fecha del 1 de julio, cuando zPIV v2 se volvió gastable, el recuento total de masternode aumentó en aprox. 260 y nuestra dificultad promedio de staking de red también ha visto un aumento de alrededor de 180k a 190k. Por lo tanto, parece haber cierta correlación de que gran parte del zPIV convertido puede haber sido devuelto a nuestra red como nuevos masternodes o en staking.


chart from PIVX Explorer


Gráfica del Explorador de PIVX

Ahora la pregunta sería, ¿por qué todavía tenemos 1,58 millones de zPIV sin gastar? Esto puede deberse a wallets perdidas y/o eliminadas, a una contraseña olvidada, muchos usuarios aún no saben que ahora es gastable, quieren mantenerlos privados (si son elegibles) o son zPIV v1 heredados que aún no son gastables (hasta el próximo lanzamiento de la wallet v4.0 con PR #936) etc.

Una vez que se lance la v4.0.0 con todos los zPIV gastables, garantizará que todos los usuarios podrán transferir sus monedas libremente, y los desarrolladores finalmente podrán comenzar a investigar y trabajar en la función de privacidad de PIVX, seguido de una redacción formal sobre lo que se propone y por qué.

Pero por ahora, la gran cantidad de trabajo que nuestros desarrolladores core y desarrolladores de la comunidad están poniendo en PIVX es simplemente asombrosa y proporciona una prueba fehaciente de bien que continuará el desarrollo de PIVX en el futuro.

Major Development Target Dates

2019 Q3 

  • V4.0.0 wallet release (mandatory update)
A %d blogueros les gusta esto: